Generation of real-time trigger-based digital feed

ABSTRACT

At least one aspect of this technical solution is directed to a system for invoking account opportunities for support accounts, the system including a data processing system comprising memory and one or more processors to receive, from one or more external data sources, a plurality of opportunity events indicating modifications for candidate electronic transactions, select, in response to receipt of the plurality of opportunity events, a participant object including a support service identifier associated with a support service, and a participant service identifier associated with a participant service, filter the plurality of opportunity events based at least on a first opportunity metric associated with the participant object to construct a plurality of opportunity objects, rank the plurality of opportunity objects based at least on a determination that the opportunity object satisfies a second opportunity metric associated with the participant object, transmit, to a computing device linked with the participant object, the ranked plurality of opportunity objects, receive, from the computing device, a selection of one or more of the ranked plurality of opportunity objects, generate, responsive to the selection of the one or more of the ranked opportunity objects, a link between the participant object and the support service, and authorize the participant object to the support service based on the link.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. § 119 toU.S. Provisional Patent Application Ser. No. 63/056,294, entitled“GENERATION OF REAL-TIME TRIGGER-BASED DIGITAL FEED,” filed Jul. 24,2020, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

This disclosure relates generally to digital healthcare infrastructure,and more particularly to generation of a real-time trigger-based digitalfeed.

BACKGROUND

Participants of a health care program can conduct an electronictransaction for goods or services. Due to the large number of availablesources for goods or services, and the varying parameters associatedwith electronic transactions, it can be challenging to efficiently andaccurately select a source for the goods or services for a participantwithout wasting resource utilization or introducing latency or delays.

SUMMARY OF THE DISCLOSURE

Health care opportunities are increasing in complexity and scope inresponse to the expansion of health care services available to healthcare consumers. Participants in various health care support programs andhealth care accounts face increasingly complex and interwovenopportunities with time-sensitive conditions and complexinterdependencies. However, conventional systems may not effectivelyfeed opportunities associated with such services and accountseffectively or timely to a participant, resulting in a loss ofopportunities due to lack of computational technological systems torapidly and securely communicate with heterogeneous systems centered ona participant's associations with services coupled to those systems.Thus, systems and methods of this technical solution provide cangenerate a real-time trigger-based digital feed.

At least one aspect of this technical solution is directed to a systemfor invoking account opportunities for support accounts, the systemincluding a data processing system comprising memory and one or moreprocessors to receive, from one or more external data sources, aplurality of opportunity events indicating modifications for candidateelectronic transactions, select, in response to receipt of the pluralityof opportunity events, a participant object including a support serviceidentifier associated with a support service, and a participant serviceidentifier associated with a participant service, filter the pluralityof opportunity events based at least on a first opportunity metricassociated with the participant object to construct a plurality ofopportunity objects, rank the plurality of opportunity objects based atleast on a determination that the opportunity object satisfies a secondopportunity metric associated with the participant object, transmit, toa computing device linked with the participant object, the rankedplurality of opportunity objects, receive, from the computing device, aselection of one or more of the ranked plurality of opportunity objects,generate, responsive to the selection of the one or more of the rankedopportunity objects, a link between the participant object and thesupport service, and authorize the participant object to the supportservice based on the link.

At least one aspect of this technical solution is directed to a systemwhere the data processing system further includes a machine learningengine communicatively coupled to the memory and the one or moreprocessors, and is operable to configure, by the processor, a machinelearning engine based at least partially on the received selection ofthe one or more ranked opportunity objects by modifying at least one ofthe first opportunity metric and the second opportunity metric.

At least one aspect of this technical solution is directed to systemwhere the data processing system is further operable to filter, by theprocessor, the opportunity objects based at least partially on adetermination that one or more of the opportunity objects satisfy atimestamp threshold associated with the participant object.

At least one aspect of this technical solution is directed to a systemwhere the received selection is received at a selection time satisfyingthe timestamp threshold.

At least one aspect of this technical solution is directed to a systemwhere the machine learning engine is further operable to modify at leastone of the first opportunity metric and the second opportunity metric.

At least one aspect of this technical solution is directed to a systemwhere the first opportunity metric comprises a participant compatibilitymetric associated with the participant service and the support service.

At least one aspect of this technical solution is directed to a systemof claim 1, where the second opportunity metric comprises a participantinteraction metric associated with the participant object and at leastone of the opportunity objects.

At least one aspect of this technical solution is directed to a systemwhere the opportunity event comprises a state change of the participantobject.

At least one aspect of this technical solution is directed to a systemwhere the opportunity event comprises a state change of the participantservice.

At least one aspect of this technical solution is directed to a systemwhere the support service identifier identifies a support record of anindividual associated with the support service and the participantservice.

At least one aspect of this technical solution is directed to a systemwhere the data processing system is further operable to obtain, by theprocessor, the support service at a remote support account system.

At least one aspect of this technical solution is directed to a systemwhere the data processing system is further operable to obtain, by theprocessor, the participant service at a remote financial account system.

At least one aspect of this technical solution is directed to a systemwhere the data processing system is further operable to obtain theparticipant object and the participant service identifier by a firstremote communication interface.

At least one aspect of this technical solution is directed to a systemwhere the data processing system is further operable to obtain theopportunity objects by a second remote communication interface.

At least one aspect of this technical solution is directed to a methodfor invoking account opportunities for particular support care accounts,the method including receiving, from one or more external data sources,a plurality of opportunity events indicating modifications of candidateelectronic transactions, selecting, in response to receipt of theplurality of opportunity events, a participant object including asupport service identifier associated with a support service, and aparticipant service identifier associated with a participant service,filtering the plurality of opportunity events based at least on a firstopportunity metric associated with the participant object to construct aplurality of opportunity objects, ranking the plurality of opportunityobjects based at least on a determination that the opportunity objectsatisfies a second opportunity metric associated with the participantobject, transmitting, to a computing device linked with the participantobject, the ranked plurality of opportunity objects, receiving, from thecomputing device, a selection of one or more of the ranked plurality ofopportunity objects, and generating, in response to the selection of theone or more of the ranked opportunity objects, a link between theparticipant object and the support service, and authorizing theparticipant object to the support service based on the link.

At least one aspect of this technical solution is directed to a methodfurther including configuring a machine learning engine based at leastpartially on the received selection of the one or more rankedopportunity objects, and modifying at least one of the first opportunitymetric and the second opportunity metric in response to the configuringthe machine learning engine.

At least one aspect of this technical solution is directed to a methodwhere the filtering further includes filtering the opportunity objectsbased at least partially on a determination that one or more of theopportunity objects satisfy a timestamp threshold associated with theparticipant object.

At least one aspect of this technical solution is directed to a methodwhere the received selection is received at a selection time satisfyingthe timestamp threshold.

At least one aspect of this technical solution is directed to a computerreadable medium including one or more instructions stored thereon andexecutable by a processor to receive, from one or more external datasources, a plurality of opportunity events indicating modifications forcandidate electronic transactions, select, at the processor, in responseto receipt of the plurality of opportunity events, a participant objectincluding a support service identifier associated with a supportservice, and a participant service identifier associated with aparticipant service, and filter, by the processor, the plurality ofopportunity events based at least on a first opportunity metricassociated with the participant object, and rank, by the processor, theplurality of opportunity objects based at least on a determination thatthe opportunity object satisfies a second opportunity metric associatedwith the participant object, transmit, to a computing device linked withthe participant object, the ranked plurality of opportunity objects,receive, by the processor, from the computing device, a selection of oneor more of the ranked plurality of opportunity objects, generate,responsive to the selection of the one or more of the ranked opportunityobjects, a link between the participant object and the support service,and authorize the participant object to the support service based on thelink.

At least one aspect of this technical solution is directed to a computerreadable medium further including one or more instructions executable bya processor to configure a machine learning engine based at leastpartially on the received selection of the one or more rankedopportunity objects by modifying at least one of the first opportunitymetric and the second opportunity metric.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects and features of the present implementations willbecome apparent to those ordinarily skilled in the art upon review ofthe following description of specific implementations in conjunctionwith the accompanying figures, wherein:

FIG. 1A illustrates an example network environment including a clientdevice in communication with a server device, in accordance with presentimplementations.

FIG. 1B illustrates an example cloud computing environment including aclient device in communication with cloud service providers, inaccordance with present implementations.

FIGS. 1C and 1D illustrate example computing devices in accordance withpresent implementations.

FIG. 2 illustrates an example cloud computing environment including anexample data processing system, in accordance with presentimplementations.

FIG. 3 illustrates an example data processing system, in accordance withpresent implementations.

FIG. 4 illustrates an example participant database system further to theexample data processing system of FIG. 3, in accordance with presentimplementations.

FIG. 5 illustrates an example opportunity database system further to theexample data processing system of FIG. 3, in accordance with presentimplementations.

FIG. 6 illustrates an example electronic device associated with anexample data processing system, in accordance with presentimplementations.

FIG. 7 illustrates an example method of generating a real-timetrigger-based digital feed, in accordance with present implementations.

FIG. 8 illustrates an example method of generating a real-timetrigger-based digital feed further to the method of FIG. 7, inaccordance with present implementations.

DETAILED DESCRIPTION

The present implementations will now be described in detail withreference to the drawings, which are provided as illustrative examplesof the implementations so as to enable those skilled in the art topractice the implementations and alternatives apparent to those skilledin the art. Notably, the figures and examples below are not meant tolimit the scope of the present implementations to a singleimplementation, but other implementations are possible by way ofinterchange of some or all of the described or illustrated elements.Moreover, where certain elements of the present implementations can bepartially or fully implemented using known components, only thoseportions of such known components that are necessary for anunderstanding of the present implementations will be described, anddetailed descriptions of other portions of such known components will beomitted so as not to obscure the present implementations.Implementations described as being implemented in software should not belimited thereto, but can include implementations implemented inhardware, or combinations of software and hardware, and vice-versa, aswill be apparent to those skilled in the art, unless otherwise specifiedherein. In the present specification, an implementation showing asingular component should not be considered limiting; rather, thepresent disclosure is intended to encompass other implementationsincluding a plurality of the same component, and vice-versa, unlessexplicitly stated otherwise herein. Moreover, applicants do not intendfor any term in the specification or claims to be ascribed an uncommonor special meaning unless explicitly set forth as such. Further, thepresent implementations encompass present and future known equivalentsto the known components referred to herein by way of illustration.

A data processing system can assist in identifying and executing healthcare opportunities relevant to health conditions and support servicesrelated to and individualized to particular participants of the dataprocessing system and one or more support services. The data processingsystem can determine conditions, triggers or similar states or changesin state of support services or offerings to search for opportunitiesrelevant to individual participants. Actions executable by the dataprocessing system can include identifying new opportunities based oninformation from one or more third party data sources, creating a listof opportunities enumerated or ranked based on relevance to theparticipant, and proactively providing various relevant opportunities toa participant by a graphical user interface at a participant computingdevice.

The data processing system can also invoke, receive, or apply, forexample, various triggers to determine when to identify newopportunities. These triggers can include onboarding of a newparticipant to the data processing system, a card swipe by theparticipant at a merchant payment portal, point-of-sale terminal, forexample, a real-time transaction between the participant and a linkedhealth service account or service. The data processing system can alsoassociate triggers with, for example, a particular calendar event, aparticular season or seasonality recurrence, or based on any othertime-interval proactively established by the data processing system, theparticipant, or the third party external support service, for example.The data processing system can receive, generate, process, modify, ortransform, for example, data from external third party systems includingprescriptions, drug composition and tracking information, preferred or“home” pharmacy selections, insurance plan memberships and selections,chronic conditions, insurance claim history. Data can also includeinsurance and spending history including health savings accounts, andcredit card transactions, for example. The data processing system cansupport multiple types of outputs, including filters, notificationsregarding various aspects, fields or operations of opportunities,changing configurations or operations of external accounts including401(k), health savings accounts, and flexible spending accounts, forexample.

The data processing system can also include or interface with a machinelearning system to predict optimal opportunities for individual users. Amachine learning system of the data processing system can validatefeedback responses based on subsequent transaction data, and candetermine whether or not to send notifications based on interactionfeedback indicating a likelihood of a participant to select, execute, orview, for example, a particular opportunity.

Opportunities can be opportunity events and opportunity objects.Opportunity events can represent changes in state, for example, of aservice or product relevant to a participant. Opportunity objects canencapsulate various characteristics of opportunities relevant to aparticipant, and can facilitate execution of various transaction withexternal healthcare support services, platforms, or accounts, forexample. Opportunities can be related to pharmacy services, and canprompt a user to save expense in transacting with a particular pharmacyfor prescriptions or other goods or service with that pharmacy. Savingscould take the form of coupons directly with the pharmacy, orpartnerships with external discount programs, for example. Opportunitiescan also be related to financial or monetary accounts assigned to theparticipant. For example, an opportunity can allow a participant tomaximize or modify a recurring or one-time contribution to a financialaccount. Accounts can include health-savings accounts, flexible spendingaccounts, checking accounts, credit accounts, and rewards accounts, forexample. One-time or recurring contributions can also include annual oryear-end contributions. For example, if a participant still has moneyleft in their FSA within 90 days of the end of their plan year, the dataprocessing system can recognize that state as an opportunity event, andgenerate and provide an opportunity object including a targeted coupon,dependent on their balance, to shop at a store accepting flexiblespending account funds.

For purposes of reading the description of the various implementationsbelow, the following descriptions of the sections of the specificationand their respective contents can be helpful:

Section A describes a network environment and computing environmentwhich can be useful for practicing implementations described herein.

Section B describes implementations of systems and methods forgeneration of a real-time trigger-based digital feed.

A. Computing and Network Environment

Prior to discussing specific implementations of the present solution, itcan be helpful to describe aspects of the operating environment as wellas associated system components (e.g., hardware elements) in connectionwith the methods and systems described herein. Referring to FIG. 1A, animplementation of a network environment is depicted. In brief overview,the network environment includes one or more clients 102 a-102 n (alsogenerally referred to as local machine(s) 102, client(s) 102, clientnode(s) 102, client machine(s) 102, client computer(s) 102, clientdevice(s) 102, endpoint(s) 102, or endpoint node(s) 102) incommunication with one or more servers 106 a-106 n (also generallyreferred to as server(s) 106, node 106, or remote machine(s) 106) viaone or more networks 104. In some implementations, a client 102 has thecapacity to function as both a client node seeking obtain to resourcesprovided by a server and as a server providing obtain to hostedresources for other clients 102 a-102 n.

Although FIG. 1A shows a network 104 between the clients 102 and theservers 106, the clients 102 and the servers 106 can be on the samenetwork 104. In some implementations, there are multiple networks 104between the clients 102 and the servers 106. In one of theseimplementations, a network 104′ (not shown) can be a private network anda network 104 can be a public network. In another of theseimplementations, a network 104 can be a private network and a network104′ a public network. In still another of these implementations,networks 104 and 104′ can both be private networks.

The network 104 can be connected via wired or wireless links. Wiredlinks can include Digital Subscriber Line (DSL), coaxial cable lines, oroptical fiber lines. The wireless links can include BLUETOOTH, Wi-Fi,Worldwide Interoperability for Microwave Access (WiMAX), an infraredchannel or satellite band. The wireless links can also include anycellular network standards used to communicate among mobile devices,including standards that qualify as 1G, 2G, 3G, or 4G. The networkstandards can qualify as one or more generation of mobiletelecommunication standards by fulfilling a specification or standardssuch as the specifications maintained by International TelecommunicationUnion. The 3G standards, for example, can correspond to theInternational Mobile Telecommunications-2000 (IMT-2000) specification,and the 4G standards can correspond to the International MobileTelecommunications Advanced (IMT-Advanced) specification. Examples ofcellular network standards include AMPS, GSM, GPRS, UMTS, LTE, LTEAdvanced, Mobile WiMAX, and WiMAX-Advanced. Cellular network standardscan use various channel access methods e.g. FDMA, TDMA, CDMA, or SDMA.In some implementations, different types of data can be transmitted viadifferent links and standards. In other implementations, the same typesof data can be transmitted via different links and standards.

The network 104 can be any type and/or form of network. The geographicalscope of the network 104 can vary widely and the network 104 can be abody area network (BAN), a personal area network (PAN), a local-areanetwork (LAN), e.g. Intranet, a metropolitan area network (MAN), a widearea network (WAN), or the Internet. The topology of the network 104 canbe of any form and can include, e.g., any of the following:point-to-point, bus, star, ring, mesh, or tree. The network 104 can bean overlay network which is virtual and sits on top of one or morelayers of other networks 104′. The network 104 can be of any suchnetwork topology as known to those ordinarily skilled in the art capableof supporting the operations described herein. The network 104 canutilize different techniques and layers or stacks of protocols,including, e.g., the Ethernet protocol, the internet protocol suite(TCP/IP), the ATM (Asynchronous Transfer Mode) technique, the SONET(Synchronous Optical Networking) protocol, or the SDH (SynchronousDigital Hierarchy) protocol. The TCP/IP internet protocol suite caninclude application layer, transport layer, internet layer (including,e.g., IPv6), or the link layer. The network 104 can be a type of abroadcast network, a telecommunications network, a data communicationnetwork, or a computer network.

In some implementations, the system can include multiple,logically-grouped servers 106. In one of these implementations, thelogical group of servers can be referred to as a server farm 38 or amachine farm 38. In another of these implementations, the servers 106can be geographically dispersed. In other implementations, a machinefarm 38 can be administered as a single entity. In still otherimplementations, the machine farm 38 includes a plurality of machinefarms 38. The servers 106 within each machine farm 38 can beheterogeneous—one or more of the servers 106 or machines 106 can operateaccording to one type of operating system platform (e.g., WINDOWS NT,manufactured by Microsoft Corp. of Redmond, Wash.), while one or more ofthe other servers 106 can operate on according to another type ofoperating system platform (e.g., Unix, Linux, or Mac OS X).

In one implementation, servers 106 in the machine farm 38 can be storedin high-density rack systems, along with associated storage systems, andlocated in an enterprise data center. In this implementation,consolidating the servers 106 in this way can improve systemmanageability, data security, the physical security of the system, andsystem performance by locating servers 106 and high performance storagesystems on localized high performance networks. Centralizing the servers106 and storage systems and coupling them with advanced systemmanagement tools allows more efficient use of server resources.

The servers 106 of each machine farm 38 do not need to be physicallyproximate to another server 106 in the same machine farm 38. Thus, thegroup of servers 106 logically grouped as a machine farm 38 can beinterconnected using a wide-area network (WAN) connection or ametropolitan-area network (MAN) connection. For example, a machine farm38 can include servers 106 physically located in different continents ordifferent regions of a continent, country, state, city, campus, or room.Data transmission speeds between servers 106 in the machine farm 38 canbe increased if the servers 106 are connected using a local-area network(LAN) connection or some form of direct connection. Additionally, aheterogeneous machine farm 38 can include one or more servers 106operating according to a type of operating system, while one or moreother servers 106 execute one or more types of hypervisors rather thanoperating systems. In these implementations, hypervisors can be used toemulate virtual hardware, partition physical hardware, virtualizephysical hardware, and execute virtual machines that provide access tocomputing environments, allowing multiple operating systems to runconcurrently on a host computer. Native hypervisors can run directly onthe host computer. Hypervisors can include VMware ESX/ESXi, manufacturedby VMWare, Inc., of Palo Alto, Calif.; the Xen hypervisor, an opensource product whose development is overseen by Citrix Systems, Inc.;the HYPER-V hypervisors provided by Microsoft or others. Hostedhypervisors can run within an operating system on a second softwarelevel. Examples of hosted hypervisors can include VMware Workstation andVIRTUALBOX.

Management of the machine farm 38 can be de-centralized. For example,one or more servers 106 can comprise components, subsystems and modulesto support one or more management services for the machine farm 38. Inone of these implementations, one or more servers 106 providefunctionality for management of dynamic data, including techniques forhandling failover, data replication, and increasing the robustness ofthe machine farm 38. Each server 106 can communicate with a persistentstore and, in some implementations, with a dynamic store.

Server 106 can be a file server, application server, web server, proxyserver, appliance, network appliance, gateway, gateway server,virtualization server, deployment server, SSL VPN server, or firewall.In one implementation, the server 106 can be referred to as a remotemachine or a node. In another implementation, a plurality of nodes 290can be in the path between any two communicating servers.

Referring to FIG. 1B, a cloud computing environment is depicted. A cloudcomputing environment can provide client 102 with one or more resourcesprovided by a network environment. The cloud computing environment caninclude one or more clients 102 a-102 n, in communication with the cloud108 over one or more networks 104. Clients 102 can include, e.g., thickclients, thin clients, and zero clients. A thick client can provide atleast some functionality even when disconnected from the cloud 108 orservers 106. A thin client or a zero client can depend on the connectionto the cloud 108 or server 106 to provide functionality. A zero clientcan depend on the cloud 108 or other networks 104 or servers 106 toretrieve operating system data for the client device. The cloud 108 caninclude back end platforms, e.g., servers 106, storage, server farms ordata centers.

The cloud 108 can be public, private, or hybrid. Public clouds caninclude public servers 106 that are maintained by third parties to theclients 102 or the owners of the clients. The servers 106 can be locatedoff-site in remote geographical locations as disclosed above orotherwise. Public clouds can be connected to the servers 106 over apublic network. Private clouds can include private servers 106 that arephysically maintained by clients 102 or owners of clients. Privateclouds can be connected to the servers 106 over a private network 104.Hybrid clouds 108 can include both the private and public networks 104and servers 106.

The cloud 108 can also include a cloud based delivery, e.g. Software asa Service (SaaS) 110, Platform as a Service (PaaS) 112, andInfrastructure as a Service (IaaS) 114. IaaS can refer to a user rentingthe use of infrastructure resources that are needed during a specifiedtime period. IaaS providers can offer storage, networking, servers orvirtualization resources from large pools, allowing the users to quicklyscale up by accessing more resources as needed. Examples of IaaS caninclude infrastructure and services (e.g., EG-32) provided by OVHHOSTING of Montreal, Quebec, Canada, AMAZON WEB SERVICES provided byAmazon.com, Inc., of Seattle, Wash., RACKSPACE CLOUD provided byRackspace US, Inc., of San Antonio, Tex., Google Compute Engine providedby Google Inc. of Mountain View, Calif., or RIGHTSCALE provided byRightScale, Inc., of Santa Barbara, Calif. PaaS providers can offerfunctionality provided by IaaS, including, e.g., storage, networking,servers or virtualization, as well as additional resources such as,e.g., the operating system, middleware, or runtime resources. Examplesof PaaS include WINDOWS AZURE provided by Microsoft Corporation ofRedmond, Wash., Google App Engine provided by Google Inc., and HEROKUprovided by Heroku, Inc. of San Francisco, Calif. SaaS providers canoffer the resources that PaaS provides, including storage, networking,servers, virtualization, operating system, middleware, or runtimeresources. In some implementations, SaaS providers can offer additionalresources including, e.g., data and application resources. Examples ofSaaS include GOOGLE APPS provided by Google Inc., SALESFORCE provided bySalesforce.com Inc. of San Francisco, Calif., or OFFICE 365 provided byMicrosoft Corporation. Examples of SaaS can also include data storageproviders, e.g. DROPBOX provided by Dropbox, Inc. of San Francisco,Calif., Microsoft SKYDRIVE provided by Microsoft Corporation, GoogleDrive provided by Google Inc., or Apple ICLOUD provided by Apple Inc. ofCupertino, Calif.

Clients 102 can access IaaS resources with one or more IaaS standards,including, e.g., Amazon Elastic Compute Cloud (EC2), Open CloudComputing Interface (OCCI), Cloud Infrastructure Management Interface(CIMI), or OpenStack standards. Some IaaS standards can allow clientsaccess to resources over HTTP, and can use Representational StateTransfer (REST) protocol or Simple Object Access Protocol (SOAP).Clients 102 can access PaaS resources with different PaaS interfaces.Some PaaS interfaces use HTTP packages, standard Java APIs, JavaMailAPI, Java Data Objects (JDO), Java Persistence API (JPA), Python APIs,web integration APIs for different programming languages including,e.g., Rack for Ruby, WSGI for Python, or PSGI for Perl, or other APIsthat can be built on REST, HTTP, XML, or other protocols. Clients 102can access SaaS resources through the use of web-based user interfaces,provided by a web browser (e.g. GOOGLE CHROME, Microsoft INTERNETEXPLORER, or Mozilla Firefox provided by Mozilla Foundation of MountainView, Calif.). Clients 102 can also access SaaS resources throughsmartphone or tablet applications, including, e.g., Salesforce SalesCloud, or Google Drive app. Clients 102 can also access SaaS resourcesthrough the client operating system, including, e.g., Windows filesystem for DROPBOX.

In some implementations, access to IaaS, PaaS, or SaaS resources can beauthenticated. For example, a server or authentication server canauthenticate a user via security certificates, HTTPS, or API keys. APIkeys can include various encryption standards such as, e.g., AdvancedEncryption Standard (AES). Data resources can be sent over TransportLayer Security (TLS) or Secure Sockets Layer (SSL).

The client 102 and server 106 can be deployed as and/or executed on anytype and form of computing device, e.g. a computer, network device orappliance capable of communicating on any type and form of network andperforming the operations described herein. FIGS. 1C and 1D depict blockdiagrams of a computing device 100 useful for practicing animplementation of the client 102 or a server 106. As shown in FIGS. 1Cand 1D, each computing device 100 includes a central processing unit121, and a main memory unit 122. As shown in FIG. 1C, a computing device100 can include a storage device 128, an installation device 116, anetwork interface 118, an I/O controller 123, display devices 124 a-124n, a keyboard 126 and a pointing device 127, e.g. a mouse. The storagedevice 128 can include, without limitation, an operating system,software, and a software of an data processing system (DPS) 120. Asshown in FIG. 1D, each computing device 100 can also include additionaloptional elements, e.g. a memory port 103, a bridge 170, one or moreinput/output devices 130 a-130 n (generally referred to using referencenumeral 130), and a cache memory 140 in communication with the centralprocessing unit 121.

The central processing unit 121 is any logic circuitry that responds toand processes instructions fetched from the main memory unit 122. Inmany implementations, the central processing unit 121 is provided by amicroprocessor unit, e.g.: those manufactured by Intel Corporation ofMountain View, Calif.; those manufactured by Motorola Corporation ofSchaumburg, Ill.; the ARM processor and TEGRA system on a chip (SoC)manufactured by Nvidia of Santa Clara, Calif.; the POWER7 processor,those manufactured by International Business Machines of White Plains,N.Y.; or those manufactured by Advanced Micro Devices of Sunnyvale,Calif. The computing device 100 can be based on any of these processors,or any other processor capable of operating as described herein. Thecentral processing unit 121 can utilize instruction level parallelism,thread level parallelism, different levels of cache, and multi-coreprocessors. A multi-core processor can include two or more processingunits on a single computing component. Examples of multi-core processorsinclude the AMD PHENOM IIX2, INTEL CORE i5 and INTEL CORE i7.

Main memory unit 122 can include one or more memory chips capable ofstoring data and allowing any storage location to be directly accessedby the microprocessor 121. Main memory unit 122 can be volatile andfaster than storage 128 memory. Main memory units 122 can be Dynamicrandom access memory (DRAM) or any variants, including static randomaccess memory (SRAM), Burst SRAM or SynchBurst SRAM (B SRAM), Fast PageMode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM(EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended DataOutput DRAM (BEDO DRAM), Single Data Rate Synchronous DRAM (SDR SDRAM),Double Data Rate SDRAM (DDR SDRAM), Direct Rambus DRAM (DRDRAM), orExtreme Data Rate DRAM (XDR DRAM). In some implementations, the mainmemory 122 or the storage 128 can be non-volatile; e.g., non-volatileread access memory (NVRAM), flash memory non-volatile static RAM(nvSRAM), Ferroelectric RAM (FeRAM), Magnetoresistive RAM (MRAM),Phase-change memory (PRAM), conductive-bridging RAM (CBRAM),Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), Resistive RAM (RRAM),Racetrack, Nano-RAM (NRAM), or Millipede memory. The main memory 122 canbe based on any of the above described memory chips, or any otheravailable memory chips capable of operating as described herein. In theimplementation shown in FIG. 1C, the processor 121 communicates withmain memory 122 via a system bus 150 (described in more detail below).FIG. 1D depicts an implementation of a computing device 100 in which theprocessor communicates directly with main memory 122 via a memory port103. For example, in FIG. 1D the main memory 122 can be DRDRAM.

FIG. 1D depicts an implementation in which the main processor 121communicates directly with cache memory 140 via a secondary bus,sometimes referred to as a backside bus. In other implementations, themain processor 121 communicates with cache memory 140 using the systembus 150. Cache memory 140 typically has a faster response time than mainmemory 122 and is typically provided by SRAM, BSRAM, or EDRAM. In theimplementation shown in FIG. 1D, the processor 121 communicates withvarious I/O devices 130 via a local system bus 150. Various buses can beused to connect the central processing unit 121 to any of the I/Odevices 130, including a PCI bus, a PCI-X bus, or a PCI-Express bus, ora NuBus. For implementations in which the I/O device is a video display124, the processor 121 can use an Advanced Graphics Port (AGP) tocommunicate with the display 124 or the I/O controller 123 for thedisplay 124. FIG. 1D depicts an implementation of a computer 100 inwhich the main processor 121 communicates directly with I/O device 130 bor other processors 121′ via HYPERTRANSPORT, RAPIDIO, or INFINIBANDcommunications technology. FIG. 1D also depicts an implementation inwhich local busses and direct communication are mixed: the processor 121communicates with I/O device 130 a using a local interconnect bus whilecommunicating with I/O device 130 b directly.

A wide variety of I/O devices 130 a-130 n can be present in thecomputing device 100. Input devices can include keyboards, mice,trackpads, trackballs, touchpads, touch mice, multi-touch touchpads andtouch mice, microphones, multi-array microphones, drawing tablets,cameras, single-lens reflex camera (SLR), digital SLR (DSLR), CMOSsensors, accelerometers, infrared optical sensors, pressure sensors,magnetometer sensors, angular rate sensors, depth sensors, proximitysensors, ambient light sensors, gyroscopic sensors, or other sensors.Output devices can include video displays, graphical displays, speakers,headphones, inkjet printers, laser printers, and 3D printers.

Devices 130 a-130 n can include a combination of multiple input oroutput devices, including, e.g., Microsoft KINECT, Nintendo Wiimote forthe WII, Nintendo WII U GAMEPAD, or Apple IPHONE. Some devices 130 a-130n allow gesture recognition inputs through combining some of the inputsand outputs. Some devices 130 a-130 n provides for facial recognitionwhich can be utilized as an input for different purposes includingauthentication and other commands. Some devices 130 a-130 n provides forvoice recognition and inputs, including, e.g., Microsoft KINECT, SIRIfor IPHONE by Apple, Google Now or Google Voice Search.

Additional devices 130 a-130 n have both input and output capabilities,including, e.g., haptic feedback devices, touchscreen displays, ormulti-touch displays. Touchscreen, multi-touch displays, touchpads,touch mice, or other touch sensing devices can use differenttechnologies to sense touch, including, e.g., capacitive, surfacecapacitive, projected capacitive touch (PCT), in-cell capacitive,resistive, infrared, waveguide, dispersive signal touch (DST), in-celloptical, surface acoustic wave (SAW), bending wave touch (BWT), orforce-based sensing technologies. Some multi-touch devices can allow twoor more contact points with the surface, allowing advanced functionalityincluding, e.g., pinch, spread, rotate, scroll, or other gestures. Sometouchscreen devices, including, e.g., Microsoft PIXELSENSE orMulti-Touch Collaboration Wall, can have larger surfaces, such as on atable-top or on a wall, and can also interact with other electronicdevices. Some I/O devices 130 a-130 n, display devices 124 a-124 n orgroup of devices can be augment reality devices. The I/O devices can becontrolled by an I/O controller 123 as shown in FIG. 1C. The I/Ocontroller can control one or more I/O devices, such as, e.g., akeyboard 126 and a pointing device 127, e.g., a mouse or optical pen.Furthermore, an I/O device can also provide storage and/or aninstallation medium 116 for the computing device 100. In still otherimplementations, the computing device 100 can provide USB connections(not shown) to receive handheld USB storage devices. In furtherimplementations, an I/O device 130 can be a bridge between the systembus 150 and an external communication bus, e.g. a USB bus, a SCSI bus, aFireWire bus, an Ethernet bus, a Gigabit Ethernet bus, a Fibre Channelbus, or a Thunderbolt bus.

In some implementations, display devices 124 a-124 n can be connected toI/O controller 123. Display devices can include, e.g., liquid crystaldisplays (LCD), thin film transistor LCD (TFT-LCD), blue phase LCD,electronic papers (e-ink) displays, flexile displays, light emittingdiode displays (LED), digital light processing (DLP) displays, liquidcrystal on silicon (LCOS) displays, organic light-emitting diode (OLED)displays, active-matrix organic light-emitting diode (AMOLED) displays,liquid crystal laser displays, time-multiplexed optical shutter (TMOS)displays, or 3D displays. Examples of 3D displays can use, e.g.stereoscopy, polarization filters, active shutters, or autostereoscopy.Display devices 124 a-124 n can also be a head-mounted display (HMD). Insome implementations, display devices 124 a-124 n or the correspondingI/O controllers 123 can be controlled through or have hardware supportfor OPENGL or DIRECTX API or other graphics libraries.

In some implementations, the computing device 100 can include or connectto multiple display devices 124 a-124 n, which each can be of the sameor different type and/or form. As such, any of the I/O devices 130 a-130n and/or the I/O controller 123 can include any type and/or form ofsuitable hardware, software, or combination of hardware and software tosupport, enable or provide for the connection and use of multipledisplay devices 124 a-124 n by the computing device 100. For example,the computing device 100 can include any type and/or form of videoadapter, video card, driver, and/or library to interface, communicate,connect or otherwise use the display devices 124 a-124 n. In oneimplementation, a video adapter can include multiple connectors tointerface to multiple display devices 124 a-124 n. In otherimplementations, the computing device 100 can include multiple videoadapters, with each video adapter connected to one or more of thedisplay devices 124 a-124 n. In some implementations, any portion of theoperating system of the computing device 100 can be configured for usingmultiple displays 124 a-124 n. In other implementations, one or more ofthe display devices 124 a-124 n can be provided by one or more othercomputing devices 100 a or 100 b connected to the computing device 100,via the network 104. In some implementations software can be designedand constructed to use another computer's display device as a seconddisplay device 124 a for the computing device 100. For example, in oneimplementation, an Apple iPad can connect to a computing device 100 anduse the display of the device 100 as an additional display screen thatcan be used as an extended desktop. One ordinarily skilled in the artwill recognize and appreciate the various ways and implementations thata computing device 100 can be configured to have multiple displaydevices 124 a-124 n.

Referring again to FIG. 1C, the computing device 100 can comprise astorage device 128 (e.g. one or more hard disk drives or redundantarrays of independent disks) for storing an operating system or otherrelated software, and for storing application software programs such asany program related to the software 120 for the centralized stateprocessing system. Examples of storage device 128 include, e.g., harddisk drive (HDD); optical drive including CD drive, DVD drive, orBLU-RAY drive; solid-state drive (SSD); USB flash drive; or any otherdevice suitable for storing data. Some storage devices can includemultiple volatile and non-volatile memories, including, e.g., solidstate hybrid drives that combine hard disks with solid state cache. Somestorage device 128 can be non-volatile, mutable, or read-only. Somestorage device 128 can be internal and connect to the computing device100 via a bus 150. Some storage device 128 can be external and connectto the computing device 100 via a I/O device 130 that provides anexternal bus. Some storage device 128 can connect to the computingdevice 100 via the network interface 118 over a network 104, including,e.g., the Remote Disk for MACBOOK AIR by Apple. Some client devices 100may not require a non-volatile storage device 128 and can be thinclients or zero clients 102. Some storage device 128 can also be used asan installation device 116, and can be suitable for installing softwareand programs. Additionally, the operating system and the software can berun from a bootable medium, for example, a bootable CD, e.g. KNOPPIX, abootable CD for GNU/Linux that is available as a GNU/Linux distributionfrom knoppix.net.

Client device 100 can also install software or application from anapplication distribution platform. Examples of application distributionplatforms include the App Store for iOS provided by Apple, Inc., the MacApp Store provided by Apple, Inc., GOOGLE PLAY for Android OS providedby Google Inc., Chrome Webstore for CHROME OS provided by Google Inc.,and Amazon Appstore for Android OS and KINDLE FIRE provided byAmazon.com, Inc. An application distribution platform can facilitateinstallation of software on a client device 102. An applicationdistribution platform can include a repository of applications on aserver 106 or a cloud 108, which the clients 102 a-102 n can access overa network 104. An application distribution platform can includeapplication developed and provided by various developers. A user of aclient device 102 can select, purchase and/or download an applicationvia the application distribution platform.

Furthermore, the computing device 100 can include a network interface118 to interface to the network 104 through a variety of connectionsincluding, but not limited to, standard telephone lines LAN or WAN links(e.g., 802.11, T1, T3, Gigabit Ethernet, Infiniband), broadbandconnections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet,Ethernet-over-SONET, ADSL, VDSL, BPON, GPON, fiber optical includingFiOS), wireless connections, or some combination of any or all of theabove. Connections can be established using a variety of communicationprotocols (e.g., TCP/IP, Ethernet, ARCNET, SONET, SDH, Fiber DistributedData Interface (FDDI), IEEE 802.11a/b/g/n/ac CDMA, GSM, WiMax and directasynchronous connections). In one implementation, the computing device100 communicates with other computing devices 100′ via any type and/orform of gateway or tunneling protocol e.g. Secure Socket Layer (SSL) orTransport Layer Security (TLS), or the Citrix Gateway Protocolmanufactured by Citrix Systems, Inc. of Ft. Lauderdale, Fla. The networkinterface 118 can comprise a built-in network adapter, network interfacecard, PCMCIA network card, EXPRESSCARD network card, card bus networkadapter, wireless network adapter, USB network adapter, modem or anyother device suitable for interfacing the computing device 100 to anytype of network capable of communication and performing the operationsdescribed herein.

A computing device 100 of the sort depicted in FIGS. 1B and 1C canoperate under the control of an operating system, which controlsscheduling of tasks and access to system resources. The computing device100 can be running any operating system such as any of the versions ofthe MICROSOFT WINDOWS operating systems, the different releases of theUnix and Linux operating systems, any version of the MAC OS forMacintosh computers, any embedded operating system, any real-timeoperating system, any open source operating system, any proprietaryoperating system, any operating systems for mobile computing devices, orany other operating system capable of running on the computing deviceand performing the operations described herein. Typical operatingsystems include, but are not limited to: WINDOWS 2000, WINDOWS Server2012, WINDOWS CE, WINDOWS Phone, WINDOWS XP, WINDOWS VISTA, and WINDOWS7, WINDOWS RT, and WINDOWS 8 all of which are manufactured by MicrosoftCorporation of Redmond, Wash.; MAC OS and iOS, manufactured by Apple,Inc. of Cupertino, Calif.; and Linux, a freely-available operatingsystem, e.g. Linux Mint distribution (“distro”) or Ubuntu, distributedby Canonical Ltd. of London, United Kingdom; or Unix or other Unix-likederivative operating systems; and Android, designed by Google, ofMountain View, Calif., among others. Some operating systems, including,e.g., the CHROME OS by Google, can be used on zero clients or thinclients, including, e.g., CHROMEBOOKS.

The computer system 100 can be any workstation, telephone, desktopcomputer, laptop or notebook computer, netbook, ULTRABOOK, tablet,server, handheld computer, mobile telephone, smartphone or otherportable telecommunications device, media playing device, a gamingsystem, mobile computing device, or any other type and/or form ofcomputing, telecommunications or media device that is capable ofcommunication. The computer system 100 has sufficient processor powerand memory capacity to perform the operations described herein. In someimplementations, the computing device 100 can have different processors,operating systems, and input devices consistent with the device. TheSamsung GALAXY smartphones, e.g., operate under the control of Androidoperating system developed by Google, Inc. GALAXY smartphones receiveinput via a touch interface.

In some implementations, the computing device 100 is a gaming system.For example, the computer system 100 can comprise a PLAYSTATION 3, orPERSONAL PLAYSTATION PORTABLE (PSP), or a PLAYSTATION VITA devicemanufactured by the Sony Corporation of Tokyo, Japan, a NINTENDO DS,NINTENDO 3DS, NINTENDO WII, or a NINTENDO WII U device manufactured byNintendo Co., Ltd., of Kyoto, Japan, an XBOX 360 device manufactured bythe Microsoft Corporation of Redmond, Wash.

In some implementations, the computing device 100 is a digital audioplayer such as the Apple IPOD, IPOD Touch, and IPOD NANO lines ofdevices, manufactured by Apple Computer of Cupertino, Calif. Somedigital audio players can have other functionality, including, e.g., agaming system or any functionality made available by an application froma digital application distribution platform. For example, the IPOD Touchcan access the Apple App Store. In some implementations, the computingdevice 100 is a portable media player or digital audio player supportingfile formats including, but not limited to, MP3, WAV, M4A/AAC, WMAProtected AAC, AIFF, Audible audiobook, Apple Lossless audio fileformats and .mov, .m4v, and .mp4 MPEG-4 (H.264/MPEG-4 AVC) video fileformats.

In some implementations, the computing device 100 is a tablet e.g. theIPAD line of devices by Apple; GALAXY TAB family of devices by Samsung;or KINDLE FIRE, by Amazon.com, Inc. of Seattle, Wash. In otherimplementations, the computing device 100 is an eBook reader, e.g. theKINDLE family of devices by Amazon.com, or NOOK family of devices byBarnes & Noble, Inc. of New York City, N.Y.

In some implementations, the communications device 102 includes acombination of devices, e.g. a smartphone combined with a digital audioplayer or portable media player. For example, one of theseimplementations is a smartphone, e.g. the IPHONE family of smartphonesmanufactured by Apple, Inc.; a Samsung GALAXY family of smartphonesmanufactured by Samsung, Inc.; or a Motorola DROID family ofsmartphones. In yet another implementation, the communications device102 is a laptop or desktop computer equipped with a web browser and amicrophone and speaker system, e.g. a telephony headset. In theseimplementations, the communications devices 102 are web-enabled and canreceive and initiate phone calls. In some implementations, a laptop ordesktop computer is also equipped with a webcam or other video capturedevice that enables video chat and video call.

In some implementations, the status of one or more machines 102, 106 inthe network 104 are monitored, generally as part of network management.In one of these implementations, the status of a machine can include anidentification of load information (e.g., the number of processes on themachine, CPU and memory utilization), of port information (e.g., thenumber of available communication ports and the port addresses), or ofsession status (e.g., the duration and type of processes, and whether aprocess is active or idle). In another of these implementations, thisinformation can be identified by a plurality of metrics, and theplurality of metrics can be applied at least in part towards decisionsin load distribution, network traffic management, and network failurerecovery as well as any aspects of operations of the present solutiondescribed herein. Aspects of the operating environments and componentsdescribed above will become apparent in the context of the systems andmethods disclosed herein.

B. Generation of a Real-Time Trigger Based Digital Feed

Systems and methods in accordance with present implementations cangenerate opportunities for consuming healthcare products and servicesbased on detecting various promotions, prices, accounts, or productofferings by a number of healthcare support services. Presentimplementations can detect state or change in of particular promotions,prices, accounts, or product offerings linked to a healthcareparticipant and present opportunities for interacting with thosepromotions, prices, accounts, or product offerings, allowing a user toselect one or more of those opportunities and, in response, to modify ahealthcare service or modify a pattern of product consumptionindividualized to that user. Present implementations can thus include anevent control engine to govern interactions with external healthcaresystems, an opportunity engine to generate, execute, and manageopportunities associated with various external healthcare systems and aparticipant user of those healthcare systems, and a database system tostructure, modify, and manage relationships of and between theparticipant user, the opportunities, and the external healthcaresystems.

To govern interaction with external healthcare systems, an event controlengine in accordance with present implementations can include multiplegateways to external systems, and multiple internal systems to controland schedule messages between internal and external systems. Presentimplementations can include separate gateways configured to interactrespectively with third-party healthcare systems and devices associatedwith individual participants. In some implementations, gateways caninclude an application programming interface (“API”), security protocol,packetization protocol, for example, to effect communication withexternal healthcare systems and participant devices. External healthcaresystems can also be coupled to internal systems in real-time ornear-real-time by these preconfigured and secure interfaces andprotocols, allowing a highly responsive and individualized healthcareinfrastructure. Real-time or near-real-time communication can include,but is not limited to, reducing or eliminating latency of or delay incommunication to below a perceivable level by a user. As one example,latency or delay can be introduced by incompatibilities betweenthird-party computing systems, or databases, and can be reduced oreliminated by interconnection of those systems or databases throughautomated communication interfaces compatible with both. Participantdevices can include smartphones, tablets, personal computers, forexample, and can also be in real-time or near-real-time communicationwith internal systems, and thus, with external systems. Presentimplementations can include internal systems for generating and managingthese real-time or near-real-time communications, which implement highlyresponsive end-to-end interaction between a participant user of up tomultiple healthcare systems and the healthcare systems on which thatuser relies. Present implementations can also be responsive toreal-world conditions in which the system operate, including variouslimitations on bandwidth and connectivity that participant users andtheir participant devices may experience, or that healthcare systems maythemselves experience. Thus, internal systems in accordance with presentimplementations can include system scheduling and batch processing ofmessages between internal systems and the external healthcare systems,participant devices, or both.

To generate and manage opportunities tailored to a particularparticipant of a particular healthcare service or group thereof, anopportunity engine can discover opportunities by detecting variousconditions or states at one or more external healthcare systems relevantto a participant user, audit opportunities to ensure that thoseopportunities remain relevant and available to an individual participantuser, and execute those relevant and available opportunities for theparticipant user. Both the opportunity discovery and audit systems canbe responsive to triggers received from external healthcare systems thatare relevant to an individual participant user. For example, a change inprescription drug prices at a particular pharmacy can trigger anopportunity discovery or audit process for a participant if thatparticipant is currently prescribed that prescription drug, for example.

Referring now to FIG. 2, a block diagram depicting an implementation ofa system 200 comprising a centralized state processing system is shown.In brief overview, the system 200 includes an data processing system 120(“DPS”) that can receive and/or transmit data via a network 104 withparticipant computing devices 232 a-n, third-party administrator devices240 a-n, employer devices 238 a-n, point-of-sale terminals 236 a-n, orheterogeneous electronic funding sources 234 a-n. The DPS 120 caninclude a communications interface 204 that is configured with one ormore communications ports, application programming interfaces, networkprotocols (e.g., TCP/IP), authentication protocols, or securityprotocols (e.g., SSL). The DPS 120 can include, interface with, orotherwise access an event control engine 310 that controls generation,display, and the like, of opportunity objects and participant objects.The DPS 120 can include, interface with, or otherwise access anopportunity engine 320 that analyzes, transmits, executes, and the like,opportunity objects. The DPS 120 can include one or more databases ordata structures that store information to facilitate the systems andmethods of the present solution, such as database 330. The database 330can include data structures, files or otherwise categorize informationinto different databases based at least partially by object. Thedatabase 330 can also include one or more policies, profiles, merchantinformation, or historical transaction activity, and the like.

The system 120, event control engine 310, and opportunity engine 320 caneach include one or more processing units or other logic devices such asprogrammable logic array engines, modules, or circuitry designed andconstructed to facilitate managing security on a network infrastructure.The DPS 120 can include the components 100 shown in FIG. 1C or FIG. 1D,or be configured to operate as a service in cloud 108. The DPS 120 caninclude or interact with one or more servers 106 a-n and clients 102a-n. The participant computing devices 232 a-n, POS terminals 236 a-n,employer devices 238 a-n, TPA devices 240 a-n, or heterogeneouselectronic funding sources 234 a-n can each include one or morecomponent or functionality of client computing devices 102 a-n or server106 a-n.

In some implementations, the DPS 120 can employ a multitier architecturesuch as a client-server architecture in which presentation, applicationprocessing, and data management functions are logically or physicallyseparated. The presentation tier, or front-end, can include thecommunications interface 204 that can serve static content or dynamiccontent to be rendered by the client 102 (e.g., by a web browserexecuting on client 102). The presentation tier or web server caninteract or communicate with the application tier to obtain data toprovide to the client 102, computing devices, 232 a-n, TPA devices 240a-n, employer devices 238 a-n, funding sources 234 a-n, or POS terminals120 a-n. The application tier can include the event control engine 310and the opportunity engine 320. The application tier can interact withthe data tier to obtain the transaction data. The data tier can includedata persistence mechanisms (database servers, file shares, etc.) andthe data access layer that encapsulates the persistence mechanisms andexposes the data. The data tier can include databases 214. The data tiercan include an application programming interface (API) to theapplication tier. The databases 214 can include stored procedures (e.g.,SQL statements) that perform tasks with respect the stored data.

The system 200 can include, access, or otherwise communicate with one ormore third-party administrator (“TPA”) devices 240 a-n. A TPA can referto an organization that processes insurance claims or certain aspects ofemployee benefit plans for a separate entity. A TPA can refer toorganizations within the insurance industry which “administer” otherservices such as Underwriting or Customer Service. In some cases, a TPAcan handle the claims processing for employers 238 a-n that self-insuresits employees 232 a-n. Thus, the employers 238 a-n are acting as aninsurance company and underwrites the risk. The risk of loss can remainswith the employer 238 a-n, and not with the TPA 240 a-n. An insurancecompany may also use a TPA 240 a-n to manage its claims processing,provider networks, utilization review, or membership functions. The TPA240 a-n can handle many aspects of other employee benefit plans such asthe processing of retirement plans and flexible spending accounts. Manyemployee benefit plans have highly technical aspects and difficultadministration that can make using a specialized entity such as a TPA240 a-n more cost effective than doing the same processing in house.

In the health care industry, for example, TPAs 240 a-n can administerall or a portion of the claims process. TPAs 240 a-n can be contractedby a health insurer or self-insuring companies to administer services,including claims administration, premium collection, enrollment andother administrative activities. For example, an employer 238 a-n maychoose to help finance the health care costs of its employees 232 a-n bycontracting with a TPA 240 a-n to administer many aspects of aself-funded health care plan.

Administrators, such as companies or health insurance providers, canestablish electronic benefits accounts such as flexible spendingaccounts or healthcare tax benefit accounts (e.g., health savingsaccounts) for participants such as employees, subscribers, or customers.These electronic benefits accounts can provide a tax advantage for theparticipants. Administrators that establish or provide electronic taxbenefits accounts for various participants of those accounts can utilizebackend information technology infrastructure to process, analyze,monitor or manage the electronic tax benefits accounts. The tax benefitmanagement information technology infrastructure can be configured withprocessing rules that are applied to electronic transactions. Electronictransactions can include allocating funds to the tax benefit account,withdrawing funds from the tax benefit account, making a purchase withfunds from the tax benefit account, modifying a profile of the taxbenefit account, or submitting a claim. The management informationtechnology infrastructure can apply one or more rules to each type oftransaction to determine an event. As the types of transactions andrules increase in number and complexity, the types and events can alsoincrease in number and complexity, thereby consuming an increasingamount of resources of the information technology infrastructure. Forexample, events such as a card denial increases the number oftransaction attempts, communications with the server, account resets,profile corruption, or resources consumed by a point-of-sale deviceinitiating the transaction.

The employer devices 238 a-n can refer to a device used by an entity ororganization that is associated with the participant computing devices232 a-n of the employees of the employer. For example, Employer A can bea software company that has a thousand employees associated with theparticipant computing devices 232 a-n. The employees can obtain healthcare or other services, and pay for those services at a POS terminal 236a-n of the service provider.

Data packets can be generated by a device 240 a-n at an administrator.The device can refer to an administrator device (“administrator device”)such as administrator device 240 a-n. The administrator device 240 a-nmay monitor data from the various electronic benefits accountsassociated with the administrator. The accounts associated with theadministrator may be accounts that are managed or maintained by theadministrator. The administrator may be a point of contact for customersor participants of the associated accounts. In some implementations, theclient 102, which may correspond to an individual participant of theadministrator's electronic benefits account, may access the account andperform a number of actions with respect to the account, such as, fundthe account (e.g., via heterogeneous electronic funding sources 234a-n), withdraw from the account, charge the account, and the like. Theadministrator of the electronic benefits account, as the caretaker ofthe account, may adjust parameters associated with the account, such as,monthly fees, minimum running balances, etc. At the same time, the DPS120 may monitor the data, parameters, and performance of the account andstore the information under an administrator profile associated with theadministrator of the account. The DPS 120 may receive the dataassociated with the individual participants and their individualaccounts from the client's 102 and the parameter data associated withthe accounts from the administrator device 240 a-n via the network 104.

An administrator device 240 a-n can be the place where an administratormay perform various functions of the administrator, for example,functions associated with electronic benefits accounts of theadministrator. The administrator device 240 a-n is the point at anadministrator that may send requests or transaction information to theDPS 120 for further processing or data collection. The administratordevice 240 a-n may also be configured to transmit an identifierassociated with the administrator corresponding to the administratordevice 240 a-n for identification by the DPS 120. In someimplementations, the receiving of the identifier initiates a frauddetection and control process.

The administrator device 240 a-n can include hardware and software.Administrators can utilize scanners, EFTPOS terminals, touch screens andany other wide variety of hardware and software available for use withadministrator device 240 a-n. For example, an administrator can usesoftware to make adjustments to parameters associated with theirelectronic benefits accounts.

The administrator device 240 a-n can include advanced features to caterto different functionality, such as account participant forecasts andestimates, account simulation, communication with participants ofaccounts, performing actions associated with individual participantaccounts (e.g., freezing an account), collecting data from one or moreof the participant accounts, etc., all built into the administratorsoftware. The administrator device 240 a-n can be configured to executeuser-input commands with respect to the electronic benefits accounts ofthe administrator.

In some implementations, the communication interface 204 can receivedata packets. The data packets can carry one or more electronictransactions. In some cases, the data packets can carry multipleelectronic transactions. In some cases, the data packets can be receivedover a duration of time. The electronic transactions can occur over theduration of time. In some cases, the electronic transaction informationcarried via the data packets can be received by the DPS 120 inreal-time, such as responsive to the occurrence of the electronictransaction. In some cases, the DPS 120 can receive the informationabout the electronic transactions in a bulk upload or batch upload.Receiving the information about the electronic transactions in a bulkupload or batch upload can reduce computing resource utilization ornetwork bandwidth usage, thereby improving the efficiency of the DPS120. For example, the provider of the information about the electronictransactions can compress the information and generate data packetscarrying the compressed information in a single batch or bulktransmission, thereby reducing network bandwidth utilization.

The electronic transaction information carried via the data packets caninclude information that facilitates performance of the electronictransaction, or analyzing the electronic transaction to detectfraudulent activity. The electronic transaction can include a sourceidentifier pointing to a data structure storing a resource, adestination identifier corresponding to a data structure to transfer theresource, and an intermediary identifier corresponding to an entity thatprovides at least a portion of the resource stored in the datastructure. The source identifier can refer to an account identifier thatcontains the resource being transferred from a source to a destination.The source identifier can refer to an account of an employee of anemployer. The source identifier can correspond to an account associatedwith a participant computing device 232. The resource can correspond toan electronic resource or physical resource being represented in anelectronic form. The resource can refer to or include a token, currency,points, or other resource that can be transferred from the source to adestination. The destination identifier an correspond to an entity ororganization receiving the resource. The destination identifier cancorrespond to a provider of a service or good that is receiving theresource in return for performing the service or providing the good tothe employee. The intermediary identifier can correspond to an entitythat stores, holds, manages, provides, or maintains the resource. Theintermediary identifier can refer to or correspond to the employerdevice 238 a-n, a heterogeneous electronic funding source 234 a-n or TPA240 a-n.

An identifier corresponding to a data structure can refer to or includean identifier pointing to a data structure, such as a memory pointer.The identifier corresponding to a data structure can refer to or includean identifier used by a lookup to retrieve, identify, access or selectthe data structure. The identifier can label the data structure. Theidentifier can be mapped to the data structure.

The data packets or electronic transaction can be generated by a deviceat a merchant to conduct an electronic transaction at the merchant. Thedevice can refer to a point of sale terminal (“POS terminal”) such asPOS terminal 236 a-n. In some implementations, the POS terminals 236 a-nare the devices at which retail transactions are initiated. The POSterminals 236 a-n are the points at which a customer of the entity ormerchant makes a payment to the merchant in exchange for goods orservices. At the point of sale the merchant can calculate the amountowed by the customer and provide options for the customer to makepayment. The merchant can also issue a receipt for the transaction.

The POS terminal 236 a-n can include hardware and software. Merchantscan utilize weighing scales, scanners, electronic and manual cashregisters, EFTPOS terminals, touch screens and any other wide variety ofhardware and software available for use with POS terminal 236 a-n. Forexample, a pharmacy can use software to customize the item or servicesold when a customer has a special medication request.

The POS terminal 236 a-n can include advanced features to cater todifferent functionality, such as inventory management, CRM, financials,warehousing, flexible spending account transactions, etc., all builtinto the POS software. The POS terminal 236 a-n can be configured toconduct a transactions using a debit card, multipurse card, Bluetooth,near field communications, smartphone, smartwatch, mobiletelecommunications computing device, wearable communications, RFID, etc.

The DPS 120 can include a communications interface 204. Thecommunications interface 204 can execute on one or more processors of aserver. The communications interface 204 can include one or morecommunications ports and be configured with one or more networkprotocols. Communications ports can include, e.g., network ports,Ethernet ports, WAN ports, I/O ports, or software ports. Thecommunication port can be configured with a network protocol such asTransport Layer Protocols such as TCP/IP or UDP that are configured toreceive and process data packets received via a computer network. Theport can include or be associated with an IP address of a host and aprotocol type of the communication.

The communications interface 204 can receive data packets generated bythe POS terminal 236 a-n responsive to an electronic transactionresulting in transmission of a request to adjudicate a single claimagainst an electronic benefits account. In some implementations, therequest to adjudicate a single claim against the electronic benefitsaccount is transmitted responsive to a user swiping a payment card atthe POS terminal. The payment card can include identifying informationthat can be used to identify an account identifier of the electronicbenefit account (e.g., source identifier) against which to adjudicatethe claim. The data packets can include header information and payloadinformation. Multiple data packets can be strung together in a sequence.The header information can refer to TCP/IP headers that include fieldssuch as source port, destination port, sequence number, acknowledgenumber, window size, etc. The payload information of the data packet caninclude information related to the electronic transaction, the requestto adjudicate a single claim, the merchant, or the customer. The DPS 120can receive the data packet with header information and payloadinformation and process the packets to obtain information for furtherprocessing. The payload can include data identifying the POS terminal236 a-n (e.g., POS terminal 236 a) at which the electronic transactionoccurred, the merchant providing the POS terminal 236 a, a merchantcategory of the merchant, financial information associated with the userperforming the electronic transaction (e.g., via a card swipe or othercommunication technique used to perform the electronic transaction), anamount of expenditures of the electronic transaction, and otherinformation facilitating adjudication of the single claim. The datapackets (e.g., via the payload) can include the request to adjudicatethe single claim. The request can specify the electronic benefitsaccount for adjudication. The request can specify information foridentifying a policy for performing the adjudication. The payload caninclude data identifying a merchant category of the merchant, anelectronic benefits account, and a monetary amount of the electronictransaction.

The data packets can carry data identifying a merchant or merchantcategory of the merchant. In some implementations, the data carried bythe data packets include a merchant category code or identifier (e.g.,dental, medical, etc.). In some implementations, the data identifies amerchant, and the DPS 120 determines a merchant category based on theidentification of the merchant by, for example, using a merchant tomerchant category mapping or lookup table stored in database. In someimplementations, the data packets carrying the request to adjudicate thesingle claim against the electronic benefits account include a datastructure having a first field indicating a merchant identifier, asecond field indicating a total amount of expenditures, and a thirdfield indicating the electronics benefit account. In someimplementations, the data packets are generated by a merchant device(e.g., a client device 102 of a merchant) to conduct an electronictransaction at the merchant, and the data packets carry data identifyinga merchant category of the merchant, the electronic benefits accountmaintained and configured on the DPS 120, and a total monetary amount ofthe electronic transaction.

The data packets (e.g., payload of the data packets) can furtheridentify an electronic account maintained and configured on the server.The electronic account can be maintained and configured in a database214. The electronic account can correspond to a user and have a uniqueidentifier. The unique identifier can include numbers, letters,characters, symbols, etc. The electronic account can be associated withthe customer making the transaction at the merchant. The POS terminal236 a can receive or determine the electronic account identifier via acard swipe or other communication technique employed at the POS terminal236 a, which the POS 236 a can then convey to the DPS 120.

The communications interface 120 can further receive data packets (e.g.,payload information) identifying a monetary amount of the electronictransaction, such as a total amount of expenditures. The monetary amountcan be for the purchase of goods or services made at the merchant. Themonetary amount of the transaction can refer to the amount of funds inconsideration for goods or services obtained from the entity ormerchant. The merchant or entity can refer to the entity at which apoint-of-sale terminal or device used to make the transaction is locatedor with which the terminal is associated. The monetary amount can be inany currency (e.g., United States dollars) or units. The monetary amountcan be further tied to a category, such as medical services.

In some implementations, the POS terminal 236 a can generate multipledata packets for a single transaction. The multiple data packets caneach include a header and a payload. The header can indicate that themultiple data packets are to be grouped together for routing,transmission or processing purposes.

FIG. 3 illustrates an example data processing system, in accordance withpresent implementations. The example data processing system (DPS) 300can correspond to DPS 120. The DPS 300 can include one or more componentor functionality of DPS 120. The DPS 300 can include at least one theevent control engine 310. The DPS 300 can include at least oneopportunity engine 320. The DPS 300 can include at least one database330. The event control engine 310 can include at least one event messagecontroller 312. The event control engine 310 can include at least onehealth service gateway 314. The event control engine 310 can include atleast one participant gateway 316. The event control engine 310 caninclude at least one system scheduler 318. The opportunity engine 320can include at least one opportunity discovery engine 322. Theopportunity engine 320 can include at least one opportunity executiongateway 324. The opportunity engine 320 can include at least oneopportunity audit engine 326.

The event control engine 310 can generate, modify, block, transmit, andthe like, communication messages between at least the participantcomputing devices 232, the third party administrator device 240, theopportunity engine 320, and the database 330. The event control engine310 can include or be associated with one or more operating systems,virtual machines, or interpreters, for example, to generate, modify,block, transmit, or otherwise manage the communication messages. Thecommunication messages can include commands formatted as at least oneGET request, PUT request, for example. The event control engine 310 caninclude one or more logical or electronic devices including but notlimited to integrated circuits, logic gates, flip flops, gate arrays,programmable gate arrays, and the like. It is to be understood that anyelectrical, electronic, or like devices, or components associated withthe event control engine 310 can also be associated with, integratedwith, integrable with, replaced by, supplemented by, complemented by,for example, a system processor or any component thereof.

The event message controller 312 can restrict, regulate, modify, block,transmit, for example, one or more communication messages according toone or more transmission criteria or security criteria. The eventmessage controller 312 can enforce one or more security policiesincluding one or more security criteria. Here, the event messagecontroller 312 can apply a first security policy to communicationmessages associated with the participant communication devices 232.Here, the first security policy can include a user level trust zone,associated with a low trust level. Here, the event message controller312 can apply a second security policy to communication messagesassociated with the third party administrator devices 240. Here, thesecond security policy can include a third party level trust zone,associated with a low trust level. Here, the event message controller312 can apply a third security policy to communication messagesassociated with the event control engine 310 and the opportunity engine320. Here, the third security policy can include a cloud trust zone,associated with a medium trust level. It is to be understood thatvarious security policies and various trust zones include, but are notlimited to varying numbers and degrees of security encapsulation forexample. Here, the security encapsulation can include token validation,password validation, hardware key validation, symmetric encryption keyvalidation, and asymmetric encryption key validation.

The health service gateway 314 can generate one or more communicationmessages compatible with one or more of the third party administratordevices, based on communication messages received from the event messagecontroller 312. The health service gateway 314 can generate one or morecommunication messages compatible with the event message controller 312,based on communication messages received from one or more of the thirdparty administrator devices 240. Here, the health service gateway caninclude at least one application programming interface (API) compatiblewith the third party administrator devices 240 and the event messagecontroller 312. Here, the health service gateway 314 can include atleast one API to interface with third party administrator devices 240associated with multiple third party administrator services. Forexample, a third party administrator service can be a participant'shealth insurance service or a participant's prescription drug recordsservice. Here, the second security policy can securely couple the eventcontrol engine 310 to the third party administrator devices by thehealth service gateway 314, in accordance with one or more healthrecords standards. For example, health records standards may beassociated with Health Insurance Portability And Accountability Act(HIPAA) requirements for example.

The participant gateway 316 can generate one or more communicationmessages compatible with one or more of the participant computingdevices 232, based on communication messages received from the eventmessage controller 312. The participant gateway 316 can generate one ormore communication messages compatible with one or more of theparticipant computing devices 232, based on communication messagesreceived from the event message controller 312. Here, the participantgateway 316 can include at least one API compatible with the participantcomputing devices 232 and the event message controller 312. Here, theparticipant gateway 316 can encapsulate at least one opportunity objectreceived from the opportunity engine 320 and transmit the encapsulatedopportunity object to one or more of the participant computing devices232. Here, the participant gateway 316 encapsulates an opportunityobject in a JSON container, an encrypted package, a compressed package,for example. Here, the participant gateway 316 transmits the opportunityobject or the encapsulated opportunity object in accordance with thefirst security policy.

The system scheduler 318 can generate, modify, block, transmit, and thelike, communication messages associated with opportunity objects inaccordance with at least one transmission schedule or at least one batchprocessing criterion. Here, the transmission schedule is a synchronoustransmission schedule including at least one transmission intervalbetween transmission times. Here, the event control engine 310transmits, generates, for example, one or more communication messagesassociated with opportunity objects at a transmission time. Here, abatch processing criterion can include a connectivity condition betweenat least one of the participant computing devices 232 and one or more ofthe event control engine 310 and the data processing system 120. Here,the system scheduler 318 enters an asynchronous mode in response todetermining that connectivity with one or more particular participantcomputing devices 240 is below a connectivity threshold. Here, the batchprocessing criterion can include the connectivity threshold. As oneexample, a connectivity threshold can be a minimum lag, bandwidth,uptime, for example associated with a minimum ability to transmit one ormore opportunity objects. Here, the system scheduler 318 can include oneor more queues to asynchronously store, buffer, for example anycommunication messages that cannot be transmitted at a particulartransmission time due to failure to satisfy a connectivity threshold orsatisfying a batch processing criterion. Here, the system scheduler 318is selectably configurable into a synchronous mode, an asynchronousmode, or both. Here, the system scheduler 318 is selectably configurableby at least one API associated therewith.

The opportunity engine 320 can discover, audit, execute, and the like,one or more opportunity objects. Here, the opportunity engine 320 isoperatively coupled to at least one of the participant database 332 andthe opportunity database 334 to store, retrieve, modify, generate, link,delete, and the like, one or more objects associated therewith. Here,the opportunity engine 320 is operatively coupled to one or more of thethird-party administrator devices 240 by the event control engine 310.Here, the opportunity engine 320 can include one or more logical orelectronic devices including but not limited to integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike. It is to be understood that any electrical, electronic, or likedevices, or components associated with the opportunity engine 320 canalso be associated with, integrated with, integrable with, replaced by,supplemented by, complemented by, for example, a system processor or anycomponent thereof.

The opportunity discovery engine 322 can generate one or moreopportunity objects. Here, the opportunity discovery engine can generateone or more opportunity objects in response to at least one opportunitytrigger. Here, the opportunity discovery engine 322 detects anopportunity trigger based on a change in state of a health supportservice, support service, health support account, support account, forexample associated with a particular participant. Here, the opportunitydiscovery engine 322 detects the opportunity trigger by a communicationmessage from at least one of the third party administrator devices 240,through the health service gateway 314. Here, an opportunity trigger isbased on an opportunity type. As one example, an opportunity trigger canbe a change in price for a drug object associated with a participantobject. In this example, the opportunity discovery engine 322 determinesthat an opportunity can be generated or modified for the participantreflecting a price change opportunity, based on the opportunity trigger.As another example, an opportunity object can be a change in preferenceby a participant to update a preferred pharmacy. In this example, theopportunity discovery engine 322 determines that an opportunity can begenerated or modified for the participant reflecting one or more pricesassociated with drugs available from the newly selected preferredpharmacy, based on the opportunity trigger. In this example, theopportunity discovery engine 322 can generate or modify multipleopportunity objects, if the participant object for the participant islinked to multiple drug objects relevant to the newly selected pharmacy.

The opportunity execution gateway 324 can execute an opportunity object.Here, the opportunity execution gateway 324 receives an opportunityselection, activation, request, for example from one of the participantcomputing devices 240 by the participant gateway 316 of the eventcontroller engine 310. Here, the opportunity execution gateway generatesa communication message and transmits the communication message to oneof the third party administrator devices 240 by the health servicegateway 314. Here, the health service gateway 314 instructs one or moreof the third party devices 240 to execute an operation to modify atleast one of a health service, a health service account, or a financialaccount. As one example, the opportunity execution gateway can instructa third party pharmaceutical platform to apply a reduced payment to aprescription charge to a financial account associated with theparticipant and the opportunity. Thus, the opportunity execution gatewaycan directly effect a transaction outcome with a secure external healthsupport system by the technological solution of the example dataprocessing system in accordance with present implementations. Here, atleast one of the opportunity discovery engine 322 and the opportunityaudit engine 326 modifies, blocks, deletes, terminates, for example, anopportunity object executed by the opportunity execution gateway 324.Here, at least one of the opportunity discovery engine 322 and theopportunity audit engine 326 conducts a discovery process or an auditprocess in response to the execution of the opportunity object by theopportunity execution engine 324. Here, the participant computing device240 associated with the executed opportunity object queries, monitors,polls, for example, the participant gateway 316 to determine whether anyopportunity objects or a collection of opportunity objects are changed,or whether updated opportunity objects or a collection of opportunityobjects are available for transmission to the participant computingdevice 240 associated with the executed opportunity object.

The opportunity audit engine 326 can generate one or more opportunityobjects. Here, the opportunity trigger associated with the opportunityaudit engine 326 corresponds to the opportunity trigger associated withthe opportunity discovery engine. Here, the opportunity trigger causesat least one of the opportunity audit engine 326 and the opportunitydiscovery engine 322 to conduct its respective discovery or auditprocesses. Here, the opportunity audit engine 326 can convert anopportunity to “complete” in response to receiving an indication of aselection of a particular opportunity object from the participantgateway 316. Here, the opportunity audit engine 326 can convert anopportunity to “expired” in response to determining that the opportunityobject fails to satisfy a timestamp threshold associated with theopportunity object. As one example, the opportunity audit engine 326 canconvert an opportunity to “expired” in response to determining that acurrent timestamp occurs at or after a timestamp threshold. Here, theopportunity audit engine 326 modifies a state of an opportunity objector a component, portion, field, value, for example associated with astate of the opportunity object, to convert the opportunity object.Here, the opportunity audit engine 326 changes a state of a collectionof opportunities to indicate that an opportunity engine is updated.

FIG. 4 illustrates an example participant database system further to theexample data processing system of FIG. 3, in accordance with presentimplementations. Here, the example participant database system 400corresponds to the participant database 332. Here, the exampleparticipant database system 400 can include at least one of aparticipant object 410, an insurance object 420, a prescription object430, a pharmacy object 440, a participant profile object 450, and a drugobject 460. It is to be understood that the example participant databasesystem can support an arbitrary number of objects dependent only uponextrinsic characteristics of the example participant database system. Asone example, extrinsic characteristics of the example participantdatabase system can include a storage capacity thereof.

The participant object 410 can encapsulate at least one executable,module, link, and the like associated with a participant of a healthsupport system and the like. Here, the participant object can include atleast one object identifier 412, timestamp 414, participant key 416,geolocation monitor 418, insurance linker 422, prescription linker 432,pharmacy linker 442, participant profile linker 452, and opportunityobject linker 402.

The object identifier 412 contains one or more characteristicsassociated with a user of the data processing system 120. Here, theobject identifier can include one or more of a database key identifyingthe participant object, a participant identifier associated with ahealth service, a participant identifier associated with a participantcomputing device, and the like. As one example, the participantidentifier associated with the health service can include at least onean indication of an association between a participant and a particularhealth service provider, and an association between the participant anda particular health account provider. As another example, theparticipant identifier associated with the health service can include anindication that the participant is associated with a particular type ofhealth service or health account. As another example, health accounttype can be an HSA account. The timestamp 414 can indicate one or moretimes of critical events. Here, the timestamp 414 can include one ormore UNIX timestamps. Here, the timestamp 414 can include at least oneof a creation timestamp, a modification timestamp. Here, themodification timestamp is responsive to any action to the participantobject 410 by the opportunity engine 420 or any component thereof.

The participant key 416 contains a key based on multiple identifiersassociated with a participant. Here, the participant key 416 is based onat least one of an account code, an employer identifier and an employeeidentifier associated with the participant and the health serviceassociated with the participant. Here, the participant key 416 isencrypted, hashed, for example. Here, the participant key 416 isavailable as a validation key for authorization through the first,second or third security policies.

The geolocation monitor 418 contains a geolocation associated with theparticipant associated with the participant object 410. Here, thegeolocation monitor 418 stores one or more latitude and longitude valuesto designate a geolocation. Here, the geolocation monitor 418 obtains ageolocation from a participant computing device 240 associated with theparticipant object 410. Here, the geolocation monitor 418 obtains thegeolocation by the participant gateway 316. Here, the event controlengine 310 can modify the geolocation monitor 418. Here, the geolocationmonitor 418 can receive a geolocation on a constantly updating basis.The geolocation monitor 418 can also receive the geolocation on ascheduled basis in response to actions by the system scheduler 318.

The insurance linker 422 contains a dynamic link to the insurance object420. Here, the insurance linker 422 can generate, store, for example, alink, reference, for example to the insurance object 420 associated withthe participant object 410. Here, the insurance linker 422 associatesthe insurance object 420 with the participant object 410 in accordancewith one or more of an import process of participant information fromone or more third party administrator devices 240, or a selection,interaction, for example received from a participant computing device232 associated with the participant object 410.

The prescription linker 432 contains a dynamic link to the prescriptionobject 430. Here, the prescription linker 432 can generate, store, forexample, a link, reference, for example to the prescription object 430associated with the participant object 410. Here, the prescriptionlinker 432 associates the prescription object 430 with the participantobject 410 in accordance with one or more of an import process ofparticipant information from one or more third party administratordevices 240, or a selection, interaction, for example received from aparticipant computing device 232 associated with the participant object410.

The pharmacy linker 442 contains a dynamic link to the pharmacy object440. Here, the pharmacy linker 442 can generate, store, for example, alink, reference, for example to the pharmacy object 440 associated withthe participant object 410. Here, the pharmacy linker 442 associates thepharmacy object 440 with the participant object 410 in accordance withone or more of an import process of participant information from one ormore third party administrator devices 240, or a selection, interaction,for example received from a participant computing device 232 associatedwith the participant object 410.

The participant profile linker 452 contains a dynamic link to theparticipant profile object 450. Here, the participant profile linker 452can generate or store, for example, a link or reference, for example tothe participant profile object 450 associated with the participantobject 410. Here, the participant profile linker 452 associates theparticipant profile object 450 with the participant object 410 inaccordance with one or more of an import process of participantinformation from one or more third party administrator devices 240, or aselection or interaction, for example received from a participantcomputing device 232 associated with the participant object 410.

The opportunity object linker 402 contains a dynamic link to anopportunity object 510. Here, the opportunity object linker 402 cangenerate or store, for example, a link or reference, for example to theopportunity object 510 associated with the participant object 410. Here,the participant profile linker 452 associates the participant profileobject 450 with the participant object 410 in accordance with one ormore of an import process of participant information from one or morethird party administrator devices 240, or a selection or interaction,for example received from a participant computing device 232 associatedwith the participant object 410.

The insurance object 420 can encapsulate at least one executable,module, link, and the like associated with a participant of a healthsupport system and the like. Here, the insurance object is associatedwith, represents, for example, characteristics, variables, orexecutables, for example associated with a health support account, or asupport account, for example. Here, the insurance object 420 can executeto facilitate execution of one or more instructions to a health supportaccount, or support account, for example. Here, the insurance object 420can include an object identifier 424 and a provider encapsulator 426.The object identifier 424 contains one or more characteristicsassociated with an insurance entity associated with the participantobject 410 of the data processing system 120. Here, the objectidentifier 424 contains or can include one or more blocks, links, orexecutables, for example associated with at least one of the participantobject 410 or a participant associated with the participant object 410.The provider encapsulator 426 can encapsulate at least one executable,module, link, and the like associated with a health support system andthe like. Here, the object identifier 424 can include one or moreidentifiers associated with a health support account. As one example,the object identifier 424 can include one or more of a health insurancecarrier identification block, a health insurance group identificationblock, and a health insurance UUID identification block.

The prescription object 430 can encapsulate at least one executable,module, link, and the like associated with a pharmaceutical system,pharmaceutical entity, pharmaceutical account, pharmaceutical, healthmetric, or biological metric, for example, associated with theparticipant object 410 or a participant associated with the participantobject 410. Here, the prescription object 430 can include an objectidentifier 434, a prescription encapsulator 436, a participant key 416,a drug linker 462, and a pharmacy linker 442. Here, the prescriptionobject can include corresponding instances, references, for example ofone or more elements or components associated with corresponding objectsof the example participant database system. The object identifier 434contains one or more characteristics associated with a pharmaceuticalentity associated with the participant object 410 of the data processingsystem 120. Here, the object identifier 434 can include one or moreblocks, links, executables, for example associated with at least one ofthe participant object 410 or a participant associated with theparticipant object 410.

The prescription encapsulator 436 can encapsulate at least oneexecutable, module, link, and the like associated with at least onequantity, metric, volume, amount, mass, time, dosage, and the like of atleast one drug object 460. Here, the prescription encapsulator canencapsulate at least one personally-identifiable health record within asecure wrapper. Here, the prescription object 430 can securelyencapsulate at least one record of any type with the participant key416. Here, the participant key 416 decrypts for example, either alone orin combination with additional security components, the prescriptionencapsulator 436 or any wrapper for example associated therewith.

The participant key 438 contains a key based on multiple identifiersassociated with a participant. Here, the participant key 438 correspondsto the participant key 416. Here, the participant key 438 is a copy,reference, link, for example, to the participant key 416. Here, theprescription object can validate or facilitate validation ofinformation, executables, parameters, for example, contained in orassociated with the participant object 410, the insurance object 420, orthe prescription object 430.

The drug linker 462 contains a dynamic link to the drug object 460.Here, the drug linker 462 can generate, store, for example, a link,reference, for example to the drug object 460 associated with theprescription object 430. Here, the drug linker 462 associates theprescription object 430 with the drug object 460 in accordance with oneor more of an import process of participant information from one or morethird party administrator devices 240, or a selection, interaction, forexample received from a participant computing device 232 associated withthe participant object 410. Here, the drug linker 462 generates a link,reference, for example to at least one drug object 460 within aprescription associated with a participant object 410. As one example,the drug linker 462 can generate and maintain a link to a drug objectstatically or dynamically based on a drug provider by a health supportservice, support service, for example.

The pharmacy linker 442 contains a dynamic link to the pharmacy object440. Here, the pharmacy linker 442 can generate or store, for example, alink or reference, for example to the pharmacy object 440 associatedwith the prescription object 430. Here, the pharmacy linker 442associates the prescription object 430 with the pharmacy object 440 inaccordance with one or more of an import process of participantinformation from one or more third party administrator devices 240, or aselection or interaction, for example received from a participantcomputing device 232 associated with the participant object 410. Here,the pharmacy linker 442 generates a link or reference, for example to atleast one pharmacy object 440 within at least one pharmacy selectioncriterion associated with a participant object 410. As one example, thepharmacy linker 440 can generate and maintain a link to a pharmacyobject statically or dynamically based on a restriction or preferenceselection by a participant, a restriction or preference by a healthsupport service, or support service, for example.

The pharmacy object 440 can encapsulate at least one executable, module,link, and the like associated with a pharmacy system, pharmacy entity,pharmacy account, health metric, or consumer metric, for example,associated with the participant object 410 or a participant associatedwith the participant object 410. Here, the pharmacy object 440 caninclude an object identifier 444, a location identifier 446, and ageolocation identifier 448. The object identifier 444 contains one ormore characteristics associated with a pharmacy associated with theparticipant object 410 of the data processing system 120. Here, theobject identifier 444 can include one or more blocks, links,executables, or the like associated with at least one of the participantobject 410 or a participant associated with the participant object 410.The location identifier 446 contains one or more characteristicsassociated with a pharmacy location associated with the participantobject 410 of the data processing system 120. Here, the locationidentifier 446 can include one or more addresses, pharmacy locationcodes, phone numbers, and the like. The geolocation identifier 448contains one or more characteristics associated with a pharmacygeolocation associated with the participant object 410 of the dataprocessing system 120. Here, the location identifier 446 can include oneor more latitude coordinates, longitude coordinates, sphericalcoordinates, Global Positioning System (“GPS”) coordinates, pathfindingroutes, and the like.

The participant profile object 450 can encapsulate at least oneexecutable, module, link, and the like associated with a health metric,consumer metric, diagnostic assessment, prognostic assessment, healthdevice interface, or the like, associated with the participant object410 or a participant associated with the participant object 410. Here,the participant profile object can include an object identifier 454 anda diagnostic encapsulator 456. The object identifier 454 contains one ormore characteristics associated with a pharmacy associated with theparticipant object 410 of the data processing system 120. Here, theobject identifier 454 can include one or more blocks, links,executables, or the like associated with at least one of the participantobject 410 or a participant associated with the participant object 410.

The diagnostic encapsulator 456 can encapsulate at least one executable,module, link, and the like associated with at least one characteristicof the participant object 410 or a participant associated with theparticipant object 410. As one example, diagnostic encapsulator 456 caninclude at least one of medical history, prescription history, currentmedical conditions, family medical history, evaluation charts, and thelike associated with a participant object 410 or a participantassociated with the participant object 410. Here, the diagnosticencapsulator 456 can encapsulate at least one personally-identifiablehealth record within a secure wrapper. Here, the participant profileobject 430 can securely encapsulate at least one record of any type withat least one of the participant key 416 and 438. Here, at least one ofthe participant key 416 and 438 decrypts or the like, either alone or incombination with additional security components, the prescriptionencapsulator 436 or any wrapper for example associated therewith. Here,the diagnostic encapsulator 456 can secure information associatedtherewith or contained therein in accordance with one or more diagnosticsecurity protocols. As one example a diagnostic security protocol caninclude a restriction on access, decryption, for example, based on aHIPAA or like restriction.

The drug object 460 can encapsulate at least one executable, module,link, and the like associated with a drug, pharmaceutical, chemical,biochemical, composition, substance, element, or molecule, for exampleassociated with at least one of a pharmacy object 440 and a prescriptionobject 430. Here, the drug object 460 is generated based on a databasesystem, inventory system, or sales system, for example associated withat least one of a pharmacy system, health support system, healthinsurance provider, and the like. As one example, the drug object 460 isgenerated based on available drugs at one or more pharmacies associatedwith the participant and included in at least one prescription objectassociated with the participant. As another example, the drug object 460is generated based on the diagnostic encapsulator to include drugsassociated with a particular health condition of a participantassociated with the participant object 410. Here, the drug object caninclude an object identifier 464 and a drug encapsulator 466. The objectidentifier 464 contains one or more characteristics associated with adrug object associated with at least one of the participant object 410and the pharmacy object 440. Here, the object identifier 454 can includeone or more blocks, links, or executables, for example associated withat least one of the participant object 410 or a participant associatedwith the participant object 410.

The drug encapsulator 466 can encapsulate at least one executable,module, link, and the like associated with at least one characteristicof the drug object 460. As one example, the drug encapsulator 466 caninclude at least one of a chemical composition, commercial productidentifier, brand identifier, generic product identifier, and the like.Here, the drug encapsulator 466 can encapsulate at least onepersonally-identifiable health record within a secure wrapper. Here, thedrug object 460 can securely encapsulate at least one record of any typewith at least one of the participant key 416 and 438. Here, at least oneof the participant key 416 and 438 decrypts for example, either alone orin combination with additional security components, the drugencapsulator 466 or any wrapper for example associated therewith. Here,the drug encapsulator 466 can secure information associated therewith orcontained therein in accordance with one or more diagnostic securityprotocols. As one example a diagnostic security protocol can include arestriction on access, decryption, for example, based on a HIPAA or likerestriction.

FIG. 5 illustrates an example opportunity database system further to theexample data processing system of FIG. 3, in accordance with presentimplementations. Here, the example opportunity database system 500corresponds to the opportunity database 334. Here, the exampleopportunity database system 500 can include at least one of anopportunity object 510, an opportunity type object 520, an opportunityaction 530, a prescription action object 540, and an account actionobject 550.

The opportunity object 510 can encapsulate at least one executable,module, link, and the like associated with a participant of a healthsupport system and the like. Here, the opportunity object 510 isassociated with or represents, for example, characteristics, variables,or executables, for example associated with a health support account, ora support account, for example. Here, the opportunity object 510 canexecute to facilitate execution of one or more instructions to a healthsupport account, or support account, for example. Here, the opportunityobject 510 can execute a financial transaction across a plurality ofsecure and heterogeneous database system or commercial computingsystems. As one example, the opportunity object 510 can execute atransaction with a pharmacy system to obtain a pharmaceuticalprescription, including secure patient information and secure financialinformation of a participant associated with a participant object 410.In this example, the opportunity object 510 achieves the technicalsolution of secure digital communication across multiple secure systemsinvolving both financial security and patient care security protocols.Here, the opportunity object 510 can include an object identifier 512, atype linker 522, and an action linker 532. The object identifier 512contains one or more characteristics associated with the opportunityobject 510. Here, the object identifier 512 contains or can include oneor more blocks, links, or executables, for example associated withopportunity object 510.

The type linker 522 contains a dynamic link to the opportunity typeobject 520. Here, the type linker 522 can generate, or store, forexample, a link, or reference, for example to the opportunity typeobject 520 associated with the opportunity object 510. Here, the typelinker 522 associates the opportunity object 510 with the opportunitytype object 520 in accordance with one or more of an import process ofparticipant information from one or more third party administratordevices 240, or a selection, or interaction, for example received from aparticipant computing device 232 associated with the participant object410.

The action linker 532 contains a dynamic link to the opportunity actionobject 530. Here, the action linker 532 can generate, or store, forexample, a link, or reference, for example to one or more opportunityaction objects 530 associated with the opportunity object 510. Here, theaction linker 532 associates the opportunity object 510 with theopportunity action object 530 in accordance with an import process ofparticipant information from one or more third party administratordevices 240 Here, the action linker 532 associates the opportunityobject 510 with the opportunity action object 530 in accordance with aselection, or interaction, for example received from a participantcomputing device 232 associated with the participant object 410. Here,the action linker 532 associates the opportunity object 510 with theopportunity action object 530 in accordance with a scheduled updatedinitiated by a scheduling process or a batching process.

The opportunity type object 520 can encapsulate at least one executable,module, link, and the like associated with a participant of a healthsupport system and the like. Here, the opportunity object 510 isassociated with, or represents, for example, characteristics, variables,or executables, for example associated with an opportunity. As oneexample, the opportunity type object can include at least one value,metric, executable, or link, for example associated with atime-sensitive opportunity. Here, the opportunity type object 520 caninclude an object identifier 522 and a point module 524. The objectidentifier 522 contains one or more characteristics associated with theopportunity type object 510. Here, the object identifier 522 can includeone or more blocks, links, or executables, for example associated withopportunity type object 522.

The point module 524 can encapsulate at least one executable, module,link, and the like associated with an execution value of an opportunityobject associated with the opportunity type object 520. As one example,the point module 524 includes at least one value, metric, executable, orlink, for example associated with a quantitative point value forexecuting the opportunity object 510. Here, the quantitative point valuedynamically changes based on one or more opportunity or participantmetrics, factors for example. As one example, the quantitative pointvalue decreases toward zero as a current timestamp approaches atimestamp threshold.

The opportunity action object 530 can encapsulate at least oneexecutable, module, link, and the like to execute or facilitateexecution of at least one action based on at least one of theprescription action object 540 and the account action object 550. Here,the opportunity action object 530 can include one or more instructions,restrictions, security policies, interfaces, and the like to execute orfacilitate execution of at least one of the prescription action object540 and the account action object 550. Here, the opportunity actionobject 530 include an action associated with an application programminginterface (“API”) of the data processing system 120. Here, theopportunity action objects is associated with an API call through one ormore gateways of the data processing system 120. Here, the API call canbe a call to conduct actions including SwitchtoDirectDeposit,SetUpMedicineCabinet, ChangeElectronicDelivery, AttachInsuranceCarrier,AddMobilePhone, SignUpForAlerts, SignUpForElectronicTaxForm s, andEnableLocationTracking.

The prescription action object 540 can encapsulate at least oneexecutable, module, link, and the like to execute or facilitateexecution of at least one action based on the opportunity action object540. Here, the prescription action object 540 can include one or moreinstructions, restrictions, security policies, interfaces, and the liketo modify the state of at least one medical records system associatedwith the prescription action object 540. As one example, a medicalrecords system can include a pharmacy system, a health support system, ahealth insurance system, and the like. Here, the prescription actionobject 540 include a cost encapsulator 542, the prescription linker 432,and the pharmacy linker 442.

The cost encapsulator 542 can encapsulate at least one executable,module, link, and the like associated with at least one financial value,metric, for example associated with the prescription object 430. As oneexample, the cost encapsulator 542 can include at least one of a price,pricing table, pricing modifier associated with at least one of theprescription object 430, the pharmacy object 440, and the drug object460. Here, the cost encapsulator 542 can generate at least onemodification to a cost value, or metric, or the like associated with theprescription object 430, the pharmacy object 440, and the drug object460. As one example, the cost encapsulator 542 can generate aLongtermSavings value indicating a difference between cost for aprescription upon execution of an opportunity as compared to notexecuting the opportunity. It is to be understood that the costencapsulator 542 can achieve the technical solution of generating theLongtermSavings value based on multiple factors including multiple drugsthat may be subject to cost modification based on multiple prescriptionsfrom multiple health support systems and multiple pharmacy systems.Here, the cost encapsulator 542 can generate the LongtermSavings valuewith respect to a plurality of participants based on individualizedrecords.

The account action object 550 can encapsulate at least one executable,module, link, and the like to execute or facilitate execution of atleast one action based on the opportunity action object 540. Here, theaccount action object 550 can include one or more instructions,restrictions, security policies, interfaces, and the like to modify thestate of at least one financial account system associated with theaccount action object 550. As one example, a financial account systemcan include a bank account, an HSA account, a flexible spending account(“FSA”) and the like. Here, the account action object 550 can include anaccount identifier 552 and a cost encapsulator 554. Here, the accountaction object 550 can include an account identifier 552 and a costencapsulator 554. The account identifier 552 contains one or morecharacteristics associated with the financial account associated withthe opportunity action object 530. Here, the account identifier 552 caninclude one or more blocks, links, or executables, for exampleassociated with a financial account system. As one example, the accountidentifier 552 is or encapsulates a financial account number, afinancial account routing number, a financial account authorizationcode, a financial account authorization token, or a financial accountlink, for example.

The cost encapsulator 554 can encapsulate at least one executable,module, link, and the like associated with at least one financial value,or metric, for example associated with the account identifier 552. Asone example, the cost encapsulator 542 can include at least one of afinancial contribution amount, financial payment amount, financialcredit amount, or financial debit amount, for example associated withthe account identifier 552. Here, the cost encapsulator 554 can generateat least one modification to a cost value, or metric, for exampleassociated with the account identifier 552. As one example, the costencapsulator 542 can generate a MaxOutContributions value instructing afinancial account system to increase a payment to the financial accountaccording to one or more threshold criteria contained in the accountidentifier 552. It is to be understood that the cost encapsulator 554can achieve the technical solution of generating the MaxOutContributionsvalue based on secure direct communication with a financial accountsystem.

FIG. 6 illustrates an example electronic device associated with anexample data processing system, in accordance with an implementation.Here, the example electronic device 600 can include a processor, memorydevice, and display device to generate a graphical user interface, and acommunication interface to communication with the data processing systemas discussed above with respect to FIGS. 1A-D and 2. Here, the exampleelectronic device can include an opportunity summary region 602, a scoresummary region 604, an account action object region 606, and anopportunity list region 610. Here, the example electronic device 600 cangenerate a graphical user interface (“GUI”) representing, displaying,and the like, one or more of objects of FIGS. 4 and 5. Here, the exampleelectronic device 600 can include a GUI associated with a mobileoperating system. Here, Here, the example electronic device 600 isfurther operable to receive selection, input, and the like from atouch-based input system disposed thereon, therewith, for example. Here,the touch-based input system is a capacitive or a resistive touchinterface. Here, that the mobile interface can include a presentationdevice including but not limited to an LCD, LED, OLED for example.

The opportunity summary region 602 can present at least one metricassociated with one or more opportunity objects available for selectionat the example electronic device 600. Here, the opportunity summaryregion 602 presents a total number of available opportunity objects forselection. Here, the opportunity summary region 602 presents a totalnumber of available opportunity objects that have not yet been executed.

The score summary region 604 can present at least one metric associatedwith one or more opportunity objects available for selection at theexample electronic device 600. Here, the score summary region 604presents at least one execution value associated with the point module524. Here, the score summary region 604 presents an aggregation of aplurality of execution values associated with a corresponding pluralityof point modules each associated with a particular point value. Theopportunity list region 610 can present at least one opportunity object510 as a selectable GUI element. Here, the opportunity list region caninclude one or more opportunity objects 612. Here, the opportunityobjects 612 each correspond to a distinct opportunity object 510 of aplurality available at the opportunity database 334.

FIG. 7 illustrates an example method of generating a real-timetrigger-based digital feed, in accordance with present implementations.The method 700 can be performed by one or more component, system, deviceor module depicted in FIGS. 1A-6, including for example, a DPS or device600. In some implementations, at least one of the example systems 300,400, and 500 and the example device 600 performs method 700 according topresent implementations. The method 700 can be performed by one or morecomponent, system, device or module depicted in FIGS. 1A-6, includingfor example, a DPS or device 600.

At step 702, the DPS receives at least one opportunity event. The DPScan receive the opportunity event in response to one or more opportunitytriggers or in response to an import instruction.

At step 710, the DPS can select at least one participant object. In someimplementations, the example system obtains one or more participantobjects in accordance with an opportunity trigger. As one example, theDPS can obtain a participant object in response to obtaining anopportunity object associated with a health support service linked to aparticular participant object. The example system can generate at leastone participant object 410 in response to an import instruction. In someimplementations, step 710 includes at least one of steps 712 and 714. Atstep 712, the DPS can obtain a health service identifier from theparticipant object. The DPS the health service identifier from theinsurance object 420 by the insurance linker 422. At step 714, the DPSobtains a participant service identifier from the participant object. Insome implementations, the DPS obtains the participant service identifierfrom the insurance object 420 by the insurance linker 422. The method700 then continues to step 720.

At step 720, the DPS obtains at least one compatibility metricassociated with at least one of the opportunity object and theparticipant object. In some implementations, the opportunity discoveryengine 322 obtains the compatibility metric. In some implementations,the DPS generates the compatibility metric based on one or more valuesassociated with one or more of the participant profile object 450, theobject identifier 454, and the diagnostic encapsulator 456. As oneexample, the DPS generates a compatibility metric representing a maximumdistance to a pharmacy at which an opportunity for a prescriptionfulfillment can be executed. As another example, the DPS can generate acompatibility metric representing a minimum cost value for redemption ofa particular opportunity. As another example, the DPS can generate acompatibility metric blocking opportunities that do not correspond toany account associated with the provider encapsulator, prescriptionencapsulator, or drug encapsulator associated with a participant objector a participant associated with the participant object. The method 700then continues to step 730.

At step 730, the DPS determines whether the opportunity event satisfiesthe compatibility metric. In some implementations, at least one of theopportunity discovery engine 322 and the opportunity audit engine 326performs step 730. As one example, the opportunity engine blocks allopportunities greater than a maximum threshold distance from aparticipant address, or geolocation, for example. In accordance with adetermination that the opportunity event satisfies the compatibilitymetric, the method 700 continues to step 740. Alternatively, inaccordance with a determination that the opportunity event does notsatisfy the compatibility metric, the method 700 continues to step 750.At step 740, the DPS determines whether the opportunity event satisfiesat least one timestamp threshold. In some implementations, at least oneof the opportunity discovery engine 322 and the opportunity audit engine326 performs step 750. As one example, the opportunity engine blocks allopportunities with an expiration timestamp after a current time, after acurrent time minus a travel time, for example. In accordance with adetermination that the opportunity event satisfies the timestampthreshold, the method 700 continues to step 752. Alternatively, inaccordance with a determination that the opportunity event does notsatisfy the timestamp threshold, the method 700 continues to step 750.

At step 750, the DPS filters the opportunity event with a discardaction. In some implementations, at least one of the opportunitydiscovery engine 322 and the opportunity audit engine 326 performs step750. For example, the DPS can block, deletes, flags, or diverts, forexample, an existing opportunity object not satisfying the compatibilitymetric or the timestamp threshold. In some cases, the DPS can prevent,stop, abort, or terminate generation of an opportunity object notsatisfying the compatibility metric or the timestamp threshold. The DPScan generate a candidate opportunity object before satisfaction of anyor all required metrics or thresholds, or to forego generation of acandidate opportunity object before satisfaction of any or all requiredmetrics or thresholds. In some implementations, the method 700 ends atstep 750. In some implementations, the method 700 then continues to step702. At step 752, the DPS filter the opportunity event with a retainaction. In some implementations, at least one of the opportunitydiscovery engine 322 and the opportunity audit engine 326 performs step752. In some implementations, the DPS generates, saves, or stores, forexample, an opportunity event to the opportunity database 334 as anopportunity object, or partially generated opportunity object, forexample. The method 800 then continues to step 754.

At step 754, the DPS obtains at least one opportunity object associatedwith the participant object based on a retained opportunity event. Insome implementations, the DPS obtains the opportunity object 510 fromthe opportunity database 334. In some implementations, the opportunitydiscovery engine 322 performs step 720 in response to a communicationmessage received at the event message controller from at least one ofthe third party administrator devices 240. As one example, theopportunity discovery engine 322 performs step 720 in response to acommunication message from a health system, a pharmacy system, or afinancial account system operatively coupled to the DPS indicating astate thereof not associated with an existing opportunity object. Insome implementations, the opportunity audit engine 326 performs step 720in response to a communication message received at the event messagecontroller from at least one of the third party administrator devices240. As one example, the opportunity audit engine 326 performs step 820in response to a communication message from a health system, a pharmacysystem, or a financial account system operatively coupled to the DPSindicating a change in state to an opportunity object associatedtherewith. The method 700 then continues to step 730.

FIG. 8 illustrates an example method of generating a real-timetrigger-based digital feed further to the method of FIG. 7, inaccordance with present implementations. The DPS can perform method 800according to present implementations. The method 800 can be performed byone or more component, system, device or module depicted in FIGS. 1A-6,including for example, a DPS or device 600.

At step 810, the example system obtains at least one interaction metricassociated with at least one of the opportunity object and theparticipant object. The opportunity discovery engine 322 can obtain theinteraction metric. The DPS can generate the interaction metric based onone or more values associated with one or more of the action linker 532,the opportunity action 530, and the opportunity type object 520. The DPScan generate an interaction metric representing a number of times aparticipant selection of an opportunity matching a particularopportunity type occurs. The interaction metric can represent afrequency of a number of the a participant selection occurs within apredetermined time period. As one example, the interaction metric canrepresent the number of times a participant selection of a particularprescription opportunity for a particular drug is selected within amonth, or with the preceding four weeks. As another example, the examplesystem can generate an interaction metric blocking opportunities that donot correspond to any selection occurrences associated with aparticipant object or a participant associated with the participantobject. The method 800 then continues to step 820.

At step 820, the example system ranks one or more retained opportunityobjects by the interaction metric. In some implementations, at least oneof the event control engine 310 and the participant gateway 316 performsstep 820. The DPS can rank opportunity objects by one or more oftimestamp, point value, compatibility metric, and interaction metric. Asone example the example system can rank opportunity objects that havethe highest interaction metrics or compatibility metrics higher. Ranksof opportunity objects can correspond to higher positions within theopportunity list 610. The method 800 then continues to step 830. At step830, the example system receive at least one selection of at least oneopportunity object. In some implementations, at least one of the eventcontrol engine 310 and the participant gateway 316 performs step 830.The DPS can receive the selection from the example electronic device 600associated with at least one of the opportunity objects 612. In someimplementations, step 830 includes step 832. At step 832, the examplesystem receives at least one selection satisfying a timestamp threshold.The method 800 then continues to step 840.

At step 840, the example system generates at least one link between theparticipant object and a health service. At least one of the eventcontrol engine 310 and the opportunity engine 320 performs step 820. Thelink can include a communication interface, a communication protocol, ora security protocol allowing execution of one or more communicationmessages with one or more of the third party administrator devices 240.The method 800 then continues to step 850.

At step 850, the example system authorizes the participant object to thehealth service based on the generated link. The event control engine canperform step 850. The DPS can authorize the participant object byvalidating the participant key 416 or 438. The DPS can authorize theparticipant object to at least one of the event control engine, at leastone of the participant computing devices 232, and at least one of thethird party administrator devices 240. The method 800 then continues tostep 860.

At step 860, the example system configures a machine learning enginebased on the selection. In The opportunity engine can perform step 860.The DPS receives as input one or more selection responses from theelectronic devices associated with one or more of the participant object410, the insurance object 420, the prescription objet 430, the pharmacyobject 440, the participant profile object 450, the drug object 460, theopportunity object 510, the opportunity type object 520, theprescription action object 540 and the account action object 550, or ancomponent thereof. Thus, the DPS can train and modify a machine learningor like model based on input metrics from one or more of the above. Themethod 800 then continues to step 870.

At step 870, the example system modifies at least one of thecompatibility metric and the interaction metric by the machine learningengine. The opportunity engine can perform step 860. In someimplementations, step 870 includes at least one of steps 872 and 874. Atstep 872, the example system modifies at least one compatibility metric.The DPS can modify the compatibility metric based on a change in stateto one or more of the participant profile object 450, the participantobject 410, the insurance object 420, the prescription object 430, thepharmacy object 440, and the drug object 460. As one example, theexample system modifies the compatibility metric based on a change by auser to a pharmacy preference, or the importing of a new prescription orinsurance carrier associated with the participant or the participantobject. At step 874, the example system modifies at least oneinteraction metric. As another example, the example system can modifythe interaction metric based on obtaining additional selections ofopportunity objects and their associated opportunity action objects fromthe example electronic device 600. In some implementations, the method800 ends at step 870.

It should be understood that the systems described above can providemultiple ones of any or each of those components and these componentscan be provided on either a standalone machine or, in someimplementations, on multiple machines in a distributed system. Thesystems and methods described above can be implemented as a method,apparatus or article of manufacture using programming or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. In addition, the systems and methods described above can beprovided as one or more computer-readable programs embodied on or in oneor more articles of manufacture. The term “article of manufacture” asused herein is intended to encompass code or logic accessible from andembedded in one or more computer-readable devices, firmware,programmable logic, memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs,SRAMs, etc.), hardware (e.g., integrated circuit chip, FieldProgrammable Gate Array (FPGA), Application Specific Integrated Circuit(ASIC), etc.), electronic devices, a computer readable non-volatilestorage unit (e.g., CD-ROM, floppy disk, hard disk drive, etc.). Thearticle of manufacture can be accessible from a file server providingaccess to the computer-readable programs via a network transmissionline, wireless transmission media, signals propagating through space,radio waves, infrared signals, etc. The article of manufacture can be aflash memory card or a magnetic tape. The article of manufactureincludes hardware logic as well as software or programmable codeembedded in a computer readable medium that is executed by a processor.In general, the computer-readable programs can be implemented in anyprogramming language, such as LISP, PERL, C, C++, C#, PROLOG, or in anybyte code language such as JAVA. The software programs can be stored onor in one or more articles of manufacture as object code.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures areillustrative, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected,” or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents

With respect to the use of plural and/or singular terms herein, thosehaving skill in the art can translate from the plural to the singularand/or from the singular to the plural as is appropriate to the contextand/or application. The various singular/plural permutations may beexpressly set forth herein for sake of clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation, no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general,such a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

Further, unless otherwise noted, the use of the words “approximate,”“about,” “around,” “substantially,” etc., mean plus or minus tenpercent.

The foregoing description of illustrative implementations has beenpresented for purposes of illustration and of description. It is notintended to be exhaustive or limiting with respect to the precise formdisclosed, and modifications and variations are possible in light of theabove teachings or may be acquired from practice of the disclosedimplementations. It is intended that the scope of the invention bedefined by the claims appended hereto and their equivalents.

1. A system for invoking account opportunities for support accounts, thesystem comprising: a data processing system comprising memory and one ormore processors to: receive, from one or more third-party administratordevices by a real-time communication interface compatible with thethird-party administrator devices, a plurality of opportunity eventsindicating modifications for candidate electronic transactions andgenerated in response to a change to a participant service associatedwith a participant object; select, in response to receipt of theplurality of opportunity events, the participant object including asupport service identifier associated with a support service at acorresponding one of the third-party administrator devices, and aparticipant service identifier associated with the participant service;filter the plurality of opportunity events based at least on a firstopportunity metric associated with the participant object to construct aplurality of opportunity objects; rank the plurality of opportunityobjects based at least on a determination that the opportunity objectsatisfies a second opportunity metric associated with the participantobject; transmit, to a computing device linked with the participantobject, the ranked plurality of opportunity objects; receive, from thecomputing device, a selection of one or more of the ranked plurality ofopportunity objects; generate, responsive to the selection of the one ormore of the ranked opportunity objects, a link between the participantobject and the support service; and authorize, by the real-timecommunication interface, the participant object to the support servicebased on the link.
 2. The system of claim 1, wherein the data processingsystem further comprises a machine learning engine communicativelycoupled to the memory and the one or more processors, and is operableto: configure, by the processor, a machine learning engine based atleast partially on the received selection of the one or more rankedopportunity objects by modifying at least one of the first opportunitymetric and the second opportunity metric.
 3. The system of claim 1,wherein the data processing system is further operable to: filter, bythe processor, the opportunity objects based at least partially on adetermination that one or more of the opportunity objects satisfy atimestamp threshold associated with the participant object.
 4. Thesystem of claim 3, wherein the received selection is received at aselection time satisfying the timestamp threshold.
 5. The system ofclaim 1, wherein the machine learning engine is further operable tomodify at least one of the first opportunity metric and the secondopportunity metric.
 6. The system of claim 1, wherein the firstopportunity metric comprises a participant compatibility metricassociated with the participant service and the support service.
 7. Thesystem of claim 1, wherein the second opportunity metric comprises aparticipant interaction metric associated with the participant objectand at least one of the opportunity objects.
 8. The system of claim 1,wherein the opportunity event comprises a state change of theparticipant object.
 9. The system of claim 1, wherein the opportunityevent comprises a state change of the participant service.
 10. Thesystem of claim 1, wherein the support service identifier identifies asupport record of an individual associated with the support service andthe participant service.
 11. The system of claim 1, wherein the dataprocessing system is further operable to obtain, by the processor, thesupport service at a remote support account system.
 12. The system ofclaim 1, wherein the data processing system is further operable toobtain, by the processor, the participant service at a remote financialaccount system.
 13. The system of claim 1, wherein the data processingsystem is further operable to obtain the participant object and theparticipant service identifier by a first remote communicationinterface.
 14. The system of claim 1, wherein the data processing systemis further operable to obtain the opportunity objects by a second remotecommunication interface.
 15. A method for invoking account opportunitiesfor particular support care accounts, the method comprising: receiving,from one or more third-party administrator devices by a real-timecommunication interface compatible with the third-party administratordevices, a plurality of opportunity events indicating modifications ofcandidate electronic transactions and generated in response to a changeto a participant service associated with a participant object;selecting, in response to receipt of the plurality of opportunityevents, the participant object including a support service identifierassociated with a support service at a corresponding one of thethird-party administrator devices, and a participant service identifierassociated with the participant service; filtering the plurality ofopportunity events based at least on a first opportunity metricassociated with the participant object to construct a plurality ofopportunity objects; ranking the plurality of opportunity objects basedat least on a determination that the opportunity object satisfies asecond opportunity metric associated with the participant object;transmitting, to a computing device linked with the participant object,the ranked plurality of opportunity objects; receiving, from thecomputing device, a selection of one or more of the ranked plurality ofopportunity objects; and generating, in response to the selection of theone or more of the ranked opportunity objects, a link between theparticipant object and the support service; and authorizing, by thereal-time communication interface, the participant object to the supportservice based on the link.
 16. The method of claim 15, furthercomprising: configuring a machine learning engine based at leastpartially on the received selection of the one or more rankedopportunity objects; and modifying at least one of the first opportunitymetric and the second opportunity metric in response to the configuringthe machine learning engine.
 17. The method of claim 15, wherein thefiltering further comprises filtering the opportunity objects based atleast partially on a determination that one or more of the opportunityobjects satisfy a timestamp threshold associated with the participantobject.
 18. The method of claim 17, wherein the received selection isreceived at a selection time satisfying the timestamp threshold.
 19. Acomputer readable medium including one or more instructions storedthereon and executable by a processor to: receive, from one or morethird-party administrator devices by a real-time communication interfacecompatible with the third-party administrator devices, a plurality ofopportunity events indicating modifications for candidate electronictransactions and generated in response to a change to a participantservice associated with a participant object; select, at the processor,in response to receipt of the plurality of opportunity events, theparticipant object including a support service identifier associatedwith a support service at a corresponding one of the third-partyadministrator devices, and a participant service identifier associatedwith the participant service; and filter, by the processor, theplurality of opportunity events based at least on a first opportunitymetric associated with the participant object; and rank, by theprocessor, the plurality of opportunity objects based at least on adetermination that the opportunity object satisfies a second opportunitymetric associated with the participant object; transmit, to a computingdevice linked with the participant object, the ranked plurality ofopportunity objects; receive, by the processor, from the computingdevice, a selection of one or more of the ranked plurality ofopportunity objects; generate, responsive to the selection of the one ormore of the ranked opportunity objects, a link between the participantobject and the support service; and authorize, by the real-timecommunication interface, the participant object to the support servicebased on the link.
 20. The computer readable medium of claim 19, whereinthe computer readable medium further includes one or more instructionsexecutable by a processor to: configure a machine learning engine basedat least partially on the received selection of the one or more rankedopportunity objects by modifying at least one of the first opportunitymetric and the second opportunity metric.